From: Robert Treat <xzilla@users.sourceforge.net>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Preventing duplicate vacuums?
Date: 06 Feb 2004 17:32:04 -0500
Message-ID: <1076106724.30335.41.camel@camel> (raw)
In-Reply-To: <200402051351.49983.josh@agliodbs.com>
References: <200402051237.14615.josh@agliodbs.com>
<11820.1076015269@sss.pgh.pa.us>
<200402051351.49983.josh@agliodbs.com>
On Thu, 2004-02-05 at 16:51, Josh Berkus wrote:
> Tom,
>
> > Yes we do: there's a lock.
>
> Sorry, bad test. Forget I said anything.
>
> Personally, I would like to have the 2nd vacuum error out instead of blocking.
> However, I'll bet that a lot of people won't agree with me.
>
Don't know if I would agree for sure, but i the second vacuum could see
that it is being blocked by the current vacuum, exiting out would be a
bonus, since in most scenarios you don't need to run that second vacuum
so it just ends up wasting resources (or clogging other things up with
it lock)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: xzilla@users.sourceforge.net, josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Preventing duplicate vacuums?
In-Reply-To: <1076106724.30335.41.camel@camel>
* 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