Re: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron - Mailing list pgsql-admin

From John Lister
Subject Re: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron
Date
Msg-id E68310A7222D4261AE7E96703FA775F7@squarepi.com
Whole thread Raw
In response to Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron  ("Jennifer Redman" <jenred@gmail.com>)
Responses Re: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron  ("Jennifer Redman" <jenred@gmail.com>)
List pgsql-admin
>Looks like /etc/cron.d/postgresql-common
># Run VACUUM ANALYSE on all databases every 5 hours if pg_autovacuum is not
># running
>2 0,5,10,15,20 * * 1-6 root if [ -x /usr/sbin/pg_maintenance ]; then
>/usr/sbin/pg_maintenance --analyze >/dev/null; fi
>Is deprecated for postgresql versions 8.1 and higher and needs to be
>commented out by default in those packages.


The pg_maintenance scripts check the state of the autovacuuum flag in the
postgres config files. If it is enabled they simply quit and don't do
anything. Disabling autovacuum causes them to run... So you can leave them
uncommented...

Although why it causes the "Incomplete start-up packet" messages is a
mystery...


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Migration \ OID question
Next
From: "Jennifer Redman"
Date:
Subject: Re: Incomplete Startup Packet on startup and when pg_maintenance --analyze runs in cron