Nothing. I ran a query to see what other queries were running and what
other locks existed at the time. No queries running, no locks. Nothing
running at that time of night except dump, which is finished before the
vacuum job starts.
Thanks,
Scot Kreienkamp
La-Z-Boy Inc.
skreien@la-z-boy.com
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, January 05, 2009 1:05 PM
To: Scot Kreienkamp
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Vacuum problems
"Scot Kreienkamp" <SKreien@la-z-boy.com> writes:
> The nightly vacuums have been working flawlessly, but about three
weeks
> ago the vacuum full started failing. It was taking about 5-10 minutes
> normally, but all of a sudden it started hitting the command timeout
> that I have set, which is at 60 minutes. I thought that it may be a
> corrupt table or a large amount of content had been deleted from a
> database, so I built a script to loop through each database and run a
> vacuum full analyze on each table individually thinking I would find
my
> problem table. The script finished in 5 minutes!
Maybe the vacuum was blocking waiting for someone's lock on a table?
What else is running in parallel with your nightly vacuum script?
regards, tom lane
