From: Ed Loehr <ELOEHR@austin.rr.com>
To: pgsql-general@postgresql.org
To: pgsql-interfaces@postgresql.org
Subject: [GENERAL/INTERFACES] Dynamically detecting need to vacuum?
Date: Mon, 13 Dec 1999 12:37:30 -0600
Message-ID: <38553CEA.8CFFD543@austin.rr.com> (raw)
References: <14421.4341.805191.194488@ampato.aeccom.com>
I'm seeing a few intermittent show-stopper errors (some of which I've asked
about previously in these forums) which go away after vacuum is run. Pgsql
documentation recommends to vacuum nightly or after copying a large class
(not sure exactly what that means) or deleting a large number of records.
I'm tempted to run vaccum almost anytime I detect Pgsql errors (via perl
DBI) in order to try to salvage/retry the query at hand on the fly at the
cost of a much slower query from the user's perspective.
I'd like to learn how to programmatically calculate/detect when a vacuuming
is needed, and would like to hear any advice on how folks are successfully
doing this or think would best be done.
Any comments?
[Hackers: it'd be nice to have pgsql optionally take care of this...]
I'm using Pg 6.5.2 on RH Linux 6.0 2.2.5-15smp via perl DBI/DBD::Pg...
Thanks in advance,
Ed Loehr
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-interfaces@postgresql.org
Cc: ELOEHR@austin.rr.com, pgsql-general@postgresql.org
Subject: Re: [GENERAL/INTERFACES] Dynamically detecting need to vacuum?
In-Reply-To: <38553CEA.8CFFD543@austin.rr.com>
* 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