| From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "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-02 09:19:54 |
| Message-ID: | 47020D3A.7060909@gmx.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> How about getting ShareUpdateExclusiveLock on manual analyze and plain
>> AccessShareLock on autovacuum-induced analyze?
>
> Wouldn't fix the original problem because those two lock types don't
> conflict; hence might as well keep the behavior simple.
What about a new separate lock type for analyze? Couldn't that really
solve the issue? I know I'm just hand-waving here ;-)
Best Regards
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paesold | 2007-10-02 09:23:12 | Re: First steps with 8.3 and autovacuum launcher |
| Previous Message | Magnus Hagander | 2007-10-02 09:18:23 | Re: [COMMITTERS] pgsql: Use BIO functions to avoid passing FILE * pointers to OpenSSL |