From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: andy <andy@squeakycode.net>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [ADMIN] Vacuum error on database postgres
Date: Thu, 14 Sep 2006 14:57:25 -0700
Message-ID: <1158271045.29889.143.camel@dogma.v10.wvs> (raw)
In-Reply-To: <29469.1158247230@sss.pgh.pa.us>
References: <44F82150.5000809@pnlassociates.com>
<4001.1157121669@sss.pgh.pa.us>
<ee7pua$2bou$1@news.hub.org>
<27602.1158238299@sss.pgh.pa.us>
<45095CDD.8090704@squeakycode.net>
<29469.1158247230@sss.pgh.pa.us>
On Thu, 2006-09-14 at 11:20 -0400, Tom Lane wrote:
> andy <andy@squeakycode.net> writes:
> > Tom Lane wrote:
> >> andy <andy@squeakycode.net> writes:
> This behavior dates from a time when there was no good alternative.
> One possible fix today would be to make ANALYZE take
> ShareUpdateExclusive lock instead, thus ensuring there is only one
> ANALYZE at a time on a table. However I'm a bit concerned by the
> possibility that ANALYZE-inside-a-transaction could accumulate a
> whole bunch of such locks in a random order, leading at least to
> a risk of deadlocks against other ANALYZEs. (We have to hold the
> lock till commit, else we aren't fixing the problem.) Do we need a
> specialized lock type just for ANALYZE? Would sorting the target
> list of rel OIDs be enough? Perhaps it's not worth worrying about?
>
How would creating a new lock type avoid deadlocks when an ANALYZE is
accumulating the locks in random order?
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pgsql@j-davis.com, tgl@sss.pgh.pa.us, andy@squeakycode.net, alvherre@alvh.no-ip.org, pgsql-hackers@postgreSQL.org
Subject: Re: [ADMIN] Vacuum error on database postgres
In-Reply-To: <1158271045.29889.143.camel@dogma.v10.wvs>
References: <44F82150.5000809@pnlassociates.com> <4001.1157121669@sss.pgh.pa.us> <ee7pua$2bou$1@news.hub.org> <27602.1158238299@sss.pgh.pa.us> <45095CDD.8090704@squeakycode.net> <29469.1158247230@sss.pgh.pa.us> <1158271045.29889.143.camel@dogma.v10.wvs>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox