| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Alan McKay <alan(dot)mckay(at)gmail(dot)com> |
| Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PG connections going to 'waiting' |
| Date: | 2009-09-08 20:12:20 |
| Message-ID: | 20090908201220.GK549@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alan McKay escribió:
> OK, looks like the time window is exactly when we run vacuum. That
> has been running now for a couple of months no problem, but the last 2
> weekends we've been doing massive data loads which could be
> complicating things.
>
> Is vacuum a good candidate for what could be locking up the tables?
Vacuum full, which is what your script is using, locks tables. But it's
not recommended. You should be looking at an alternative vacuuming
strategy that does not involve vacuum full at all. Perhaps autovacuum,
properly tuned, is a better solution.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | miller_2555 | 2009-09-08 20:45:55 | Using symbolic links with tablespaces |
| Previous Message | Alan McKay | 2009-09-08 19:46:57 | Re: PG connections going to 'waiting' |