Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] More detail on settings for pgavd?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>,Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>,Shridhar Daithankar <shridhar_daithankar(at)myrealbox(dot)com>,pgsql-performance(at)postgresql(dot)org,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] More detail on settings for pgavd?
Date: 2003-11-21 23:04:56
Message-ID: 15608.1069455896@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance
Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Chester KustarzDate: 2003-11-21 23:53:26
Subject: Re: [HACKERS] More detail on settings for pgavd?
Previous:From: Matthew T. O'ConnorDate: 2003-11-21 22:40:45
Subject: Re: [HACKERS] More detail on settings for pgavd?

pgsql-hackers by date

Next:From: Chester KustarzDate: 2003-11-21 23:53:26
Subject: Re: [HACKERS] More detail on settings for pgavd?
Previous:From: Tom LaneDate: 2003-11-21 22:48:03
Subject: Re: conversion dumping patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group