From: Joshua D. Drake <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: When to vacuum a table?
Date: Sun, 26 Nov 2006 09:47:38 -0800
Message-ID: <4569D33A.9090700@commandprompt.com> (raw)
In-Reply-To: <19249.1164560766@sss.pgh.pa.us>
References: <1164540257.7902.0.camel@panoramix>
<c13f2d590611260443m619cd825x912b262aef5162f9@mail.gmail.com>
<20061126131147.GA4089@uio.no>
<195C9B6B-2018-474C-AA80-239A8CEA37E9@gmail.com>
<4569C04C.8090503@modgraph-usa.com>
<19249.1164560766@sss.pgh.pa.us>
> If you really want to know, read the mountains of (mostly) junk that
> have been written about replacing VACUUM in pgsql-hackers. The short
> answer (with apologies to Winston Churchill) is that VACUUM is the worst
> solution, except for all the others that have been suggested.
The lesser of 50 evils? ;)
Joshua D. Drake
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
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-performance@postgresql.org
Cc: jd@commandprompt.com, tgl@sss.pgh.pa.us, cjames@modgraph-usa.com
Subject: Re: When to vacuum a table?
In-Reply-To: <4569D33A.9090700@commandprompt.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