Re: [GENERAL] [GENERAL/INTERFACES] Dynamically detecting need to vacuum?

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