Hi @gregory.harris ,
This seems to be a bug in the newer release. The same issue has been reported earlier with Postgres DB and an issue is also logged for the same.
You can may be try moving back to version 4.3.x until this issue gets fixed.
Thanks,
Rakhi Agrawal