| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | John Lister <john(dot)lister-ps(at)kickstone(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: controlling autovacuum during the day. |
| Date: | 2008-12-17 15:28:30 |
| Message-ID: | 20081217152830.GD4453@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
John Lister wrote:
> bizarre... Its been turned off for a while, but from memory the
> autovacuum process was causing the table it was running on to be locked
> - I assumed this was an equivalent to VACUUM FULL - causing all other
> connections to wait until it had finished. Could this happen another way,
> i thought the other vacuum options acted passively... I'll turn it back
> on and see what happens...
Maybe you're doing ALTER TABLE or something else that is blocked behind
vacuum? Vacuum doesn't block INSERT, UPDATE or DELETE, but it can block
other operations that want exclusive locks on the table.
What Postgres version is this anyway?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2008-12-17 15:29:03 | Re: controlling autovacuum during the day. |
| Previous Message | John Lister | 2008-12-17 15:20:41 | Re: controlling autovacuum during the day. |