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

Re: VACUUM ANALYZE blocking both reads and writes to atable

From: Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: VACUUM ANALYZE blocking both reads and writes to atable
Date: 2008-07-01 15:26:35
Message-ID: 20080701152634.GA61808@hyperion.scode.org (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-performance
> > (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.

That is also nice to know. One more reason to upgrade to 8.3.

Thank you very much, both Alvaro and Tom, for the very insightful
discussion!

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>'
Key retrieval: Send an E-Mail to getpgpkey(at)scode(dot)org
E-Mail: peter(dot)schuller(at)infidyne(dot)com Web: http://www.scode.org

In response to

pgsql-performance by date

Next:From: Richard HuxtonDate: 2008-07-01 15:33:54
Subject: Re: Does max size of varchar influence index size
Previous:From: Franck RoutierDate: 2008-07-01 15:05:36
Subject: Re: Does max size of varchar influence index size

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