Last week the VM that the database resides on ran out of space...since that time after bringing the service back on-line getting intermittent connection issues.
Today I'm receiving the following.
ERROR: database is not accepting commands to avoid wraparound data loss in database "----" HINT: Stop the postmaster and use a standalone backend to vacuum that database. You might also need to commit or roll back old prepared transactions.
Sounds like you'll need to restart the DB in single-user mode and run a VACUUM FREEZE on the whole thing.