From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: Shridhar Daithankar <shridhar_daithankar@myrealbox.com>
Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] More detail on settings for pgavd?
Date: Fri, 21 Nov 2003 18:04:56 -0500
Message-ID: <15608.1069455896@sss.pgh.pa.us> (raw)
In-Reply-To: <200311211323.19003.josh@agliodbs.com>
References: <200311181558.45847.josh@agliodbs.com>
<200311210909.00978.josh@agliodbs.com>
<3FBE8289.1040009@zeut.net>
<200311211323.19003.josh@agliodbs.com>
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com, matthew@zeut.net, xzilla@users.sourceforge.net, shridhar_daithankar@myrealbox.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] More detail on settings for pgavd?
In-Reply-To: <15608.1069455896@sss.pgh.pa.us>
* 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