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: | 20071001234345.GC9430@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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:
> http://archives.postgresql.org/pgsql-committers/2006-09/msg00284.php
>
> 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 http://www.advogato.org/person/alvherre
"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)
http://archives.postgresql.org/pgsql-general/2007-06/msg00016.php
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-10-01 23:46:52 | Re: PG on NFS may be just a bad idea |
Previous Message | Tom Lane | 2007-10-01 23:35:36 | Re: First steps with 8.3 and autovacuum launcher |