Re: [GENERAL] [GENERAL/INTERFACES] Dynamically detecting need to vacuum? - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: [GENERAL] [GENERAL/INTERFACES] Dynamically detecting need to vacuum?
Date
Msg-id Pine.LNX.4.20.9912132250040.361-100000@localhost.localdomain
Whole thread Raw
In response to [GENERAL/INTERFACES] Dynamically detecting need to vacuum?  (Ed Loehr <ELOEHR@austin.rr.com>)
List pgsql-general
On 1999-12-13, Ed Loehr mentioned:

> documentation recommends to vacuum nightly or after copying a large class
> (not sure exactly what that means) or deleting a large number of records.

copying -- as invoked via the COPY command (in general this means
inserting, though)
large -- probably anything with triple-digit row counts
class -- table, relation; in general rows, records, data, stuff

> [Hackers:  it'd be nice to have pgsql optionally take care of this...]

There are some disabled code fragments that take into account a "vacuum
daemon". It's even on the TODO list, but vacuum itself needs to be sorted
out first.

Sorry, no free lunch here, probably.

--
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [GENERAL] Re: With what options RPM was compiled? ( Was: Czech Win1250 sorting q)
Next
From: Lamar Owen
Date:
Subject: Re: [GENERAL] Re: With what options RPM was compiled? ( Was: CzechWin1250 sorting q)