Skip site navigation (1) Skip section navigation (2)

Re: VACUUM ANALYZE blocking both reads and writes to atable

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: VACUUM ANALYZE blocking both reads and writes to atable
Date: 2008-06-30 19:04:19
Message-ID: 20080630190419.GC18252@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-performance
Tom Lane wrote:

> (2) If it's autovacuum we're talking about, it will get kicked off the
> table if anyone else comes along and wants a conflicting lock.

Not on 8.2 though.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-performance by date

Next:From: Mark RobertsDate: 2008-06-30 20:24:54
Subject: Re: Does max size of varchar influence index size
Previous:From: Tom LaneDate: 2008-06-30 19:00:40
Subject: Re: VACUUM ANALYZE blocking both reads and writes to a table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group