From: | Mike Broers <mbroers(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | after 9.2.4 patch vacuumdb -avz not analyzing all tables |
Date: | 2013-04-11 15:49:19 |
Message-ID: | CAB9893het38CbHoHOt=GZ5tuUnb77EauGidjHsyy7Mqu_4_P9w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
After patching to 9.2.4 I am noticing some mysterious behavior in my
nightly vacuumdb cron job.
I have been running vacuumdb -avz nightly for a while now, and have a
script that tells me the next day if all the tables in pg_stat_user_tables
have been vacuumed and analyzed in the last 24 hours.
Since the patch some tables do not seem to be getting analyzed. This did
not happen after I patched from earlier versions of 9.2 like 9.2.1 to
9.2.2, 9.2.3.
I pipe the output of the vacuumdb command to a log file, and there dont
appear to be any errors, its just not analyzing all the tables as it did
before. Some tables are still being analyzed ok. Its vacuuming all but a
few tables that I know are being blocked by idle in transaction sessions.
Manually analyzing the table with the psql analyze command updates the
timestamp in pg_stat_user_tables as expected. I patched about 8 database
servers to 9.2.4 and this is the only one with this problem.
Any advice?
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Ouellette | 2013-04-11 21:01:31 | Wall replay |
Previous Message | Prashanth Ranjalkar | 2013-04-11 14:01:46 | Re: with PostgreSQL 9.1.9,the stats collector process is not work! |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-04-11 16:00:28 | Re: [GSOC] questions about idea "rewrite pg_dump as library" |
Previous Message | Andrew Dunstan | 2013-04-11 15:48:23 | Re: [GSOC] questions about idea "rewrite pg_dump as library" |