No, I don't have a specific link ... re-call seeing it mentioned in another thread. You can search tracker however.
Moodle is a work in progress ... all the time ... so if you are thinking of a temp fix by altering core code to get by this, think again. Those tend to bite when you do decide it's time to update/upgrade.
Me thinks, at this point, best to get your core code under git versioning as it is very easy to acquire those small (but significant) fixes.
I can only say this as a non-programmer ... I use git ... have 4.5.3+ version and don't seem to have the issues you are having (maybe am just 'lucky'? :|).
But, then again, I also use MySQL and not Postgres.
https://docs.moodle.org/405/en/Git_for_Administrators
If you installed your moodle via 'normal' method, to get your core code under git versioning will require either a 'side load' or you could opt to use 'gitify'. See link to 'gitify' in my profile. Or a combo of acquire new code via git, and then like the old method, copy back into git acquired code directory, config.php plus any addon/plugin - before moving current code directory to codeold and renaming git acquired code directory to document root of the site, then using cli /admin/cli/upgrade.php script.
Catch 22 for you is the addon you have which doesn't have a 4.5.x compatible version.
'SoS', Ken