"Scot Kreienkamp" <SKreien@xxxxxxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
