From: Greg Stark <gsstark@mit.edu>
To: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] More detail on settings for pgavd?
Date: 21 Nov 2003 19:51:17 -0500
Message-ID: <877k1t2pkq.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <15608.1069455896@sss.pgh.pa.us>
References: <200311181558.45847.josh@agliodbs.com>
<200311210909.00978.josh@agliodbs.com>
<3FBE8289.1040009@zeut.net>
<200311211323.19003.josh@agliodbs.com>
<15608.1069455896@sss.pgh.pa.us>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Josh Berkus <josh@agliodbs.com> writes:
> > BTW, do we have any provisions to avoid overlapping vacuums? That is, to
> > prevent a second vacuum on a table if an earlier one is still running?
>
> Yes, VACUUM takes a lock that prevents another VACUUM on the same table.
The second vacuum waits for the lock to become available. If the situation got
really bad there could end up being a growing queue of vacuums waiting.
I'm not sure how likely this is as the subsequent vacuums appear to finish
quite quickly though. But then the largest table I have to play with fits
entirely in memory.
--
greg
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-performance@postgresql.org
Cc: gsstark@mit.edu, pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] More detail on settings for pgavd?
In-Reply-To: <877k1t2pkq.fsf@stark.dyndns.tv>
* 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