• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

postgres vacuumdb

G

Gorgon@

Guest
Hi folks,

Any recommendations on the best way to setup a cronjob for the vacuumdb utility for Postgres?

I know virtually nothing about postgres. I setup a cronjob a while back to run the vacuumdb utility which runs nightly as such:

/usr/bin/vacuumdb -a -q -U root

It seems to have been working fine until I got this message last night:

WARNING: Some databases have not been vacuumed in over 2 billion transactions.
You may have already suffered transaction-wraparound data loss.

According to the postgres docs, a regular vacuum should already be taking care of this. So I'm assuming I'm not using the correct options.

Any suggestions are appreciated.

Thanks,
mikeS
 
Back
Top