| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Scot Kreienkamp" <SKreien(at)la-z-boy(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Vacuum problems |
| Date: | 2009-01-05 18:04:31 |
| Message-ID: | 23710.1231178671@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Scot Kreienkamp" <SKreien(at)la-z-boy(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scot Kreienkamp | 2009-01-05 18:29:47 | Re: Vacuum problems |
| Previous Message | Oleg Bartunov | 2009-01-05 17:27:44 | Re: Adding Arabic dictionary for TSearch2.. to_tsvector('arabic'...) doesn't work.. |