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

Re: First steps with 8.3 and autovacuum launcher

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: First steps with 8.3 and autovacuum launcher
Date: 2007-10-01 23:43:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane escribió:
> [ on further thought ]
> "Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
> >> ... solving the problem 
> >> for analyze is a nice piece of low-hanging fruit that solves an 
> >> immediate problem that has been reported.
> Actually, if you wanted a low-hanging solution to that, it would
> probably be to revert this 8.2 patch:
> We did that because people were complaining of unexpected failures in
> manual ANALYZEs, but perhaps the cure is worse than the disease.

How about getting ShareUpdateExclusiveLock on manual analyze and plain
AccessShareLock on autovacuum-induced analyze?

Alvaro Herrera              
"I must say, I am absolutely impressed with what pgsql's implementation of
VALUES allows me to do. It's kind of ridiculous how much "work" goes away in
my code.  Too bad I can't do this at work (Oracle 8/9)."       (Tom Allison)

In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-10-01 23:46:52
Subject: Re: PG on NFS may be just a bad idea
Previous:From: Tom LaneDate: 2007-10-01 23:35:36
Subject: Re: First steps with 8.3 and autovacuum launcher

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