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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [GENERAL] [GENERAL/INTERFACES] Dynamically detecting need to vacuum?
Date: 1999-12-13 23:28:28
Message-ID: Pine.LNX.4.20.9912132250040.361-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-interfaces

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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 1999-12-13 23:28:34 Re: [GENERAL] Re: With what options RPM was compiled? ( Was: Czech Win1250 sorting q)
Previous Message Thomas Antepoth 1999-12-13 21:32:16 Re: [GENERAL] Installation problem on Suse linux 6.3

Browse pgsql-interfaces by date

  From Date Subject
Next Message Adriaan Joubert 1999-12-14 06:45:03 Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM?
Previous Message Mike Mascari 1999-12-13 21:29:05 Problem with LIKE in Access and ODBC