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 16:40:17 -0700
Message-ID: <1158277217.29889.146.camel@dogma.v10.wvs> (raw)
In-Reply-To: <16508.1158272742@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>
<1158271045.29889.143.camel@dogma.v10.wvs>
<16508.1158272742@sss.pgh.pa.us>
On Thu, 2006-09-14 at 18:25 -0400, Tom Lane wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
> > How would creating a new lock type avoid deadlocks when an ANALYZE is
> > accumulating the locks in random order?
>
> In itself it wouldn't. Josh Drake sketched the idea in more detail
> later: if there is a lock type used *only* for ANALYZE, then you can do
> ConditionalLockAcquire on it, and if you fail, skip the table on the
> assumption that someone else is already doing what you came to do.
>
> The whole thing seems a bit too cute/complicated though; it'd open
> various corner cases such as: ANALYZE, run complex query, query takes a
> week because it's using out-of-date stats because previous ANALYZE-r
> hadn't committed yet. I'd rather ANALYZE always analyzed than sometimes
> fell through without doing anything.
>
Couldn't you just sort by the table names, and ANALYZE the tables in
that order? Would that effectively prevent the deadlocks?
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: <1158277217.29889.146.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> <16508.1158272742@sss.pgh.pa.us> <1158277217.29889.146.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