From: Josh Berkus <josh@agliodbs.com>
To: Matt Clark <matt@ymogen.net>
To: pgsql-performance@postgresql.org
Subject: Re: Is there a reason _not_ to vacuum continuously?
Date: Wed, 17 Sep 2003 15:17:26 -0700
Message-ID: <200309171517.26841.josh@agliodbs.com> (raw)
In-Reply-To: <LFEIJBEOKGPDHCEMDGNFEECHCDAA.matt@ymogen.net>
References: <LFEIJBEOKGPDHCEMDGNFEECHCDAA.matt@ymogen.net>
Matt,
> I understand this needs an exclusive lock on the whole table, which is
> simply not possible more than once a month, if that... Workarounds/hack
> suggestions are more than welcome :-)
Would it be reasonable to use partial indexes on the table?
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, matt@ymogen.net
Subject: Re: Is there a reason _not_ to vacuum continuously?
In-Reply-To: <200309171517.26841.josh@agliodbs.com>
References: <LFEIJBEOKGPDHCEMDGNFEECHCDAA.matt@ymogen.net> <200309171517.26841.josh@agliodbs.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