pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: Otto Blomqvist <o.blomqvist@secomintl.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: pg_autovacuum not having enough suction ?
Date: Fri, 25 Mar 2005 15:17:06 -0800
Message-ID: <1111792626.5783.11.camel@jd2.commandprompt.com> (raw)
In-Reply-To: <200503252313.j2PNDFA24795@candle.pha.pa.us>
References: <200503252313.j2PNDFA24795@candle.pha.pa.us>


> > I'm not sure if autovacuum could be taught to do that --- it could
> > perhaps launch a vacuum as soon as it notices a large fraction of the
> > table got deleted, but do we really want to authorize it to launch
> > VACUUM FULL?  It'd be better to issue the vacuum synchronously
> > as part of the batch updating script, I feel.
> 
> I added this to the TODO section for autovacuum:
> 
>         o Do VACUUM FULL if table is nearly empty?

We should never automatically launch a vacuum full. That seems like a
really bad idea.

Sincerely,

Joshua D. Drake


> 
> I don't think autovacuum is every going to be smart enough to recycle
> during the delete, especially since the rows can't be reused until the
> transaction completes.
> 
> One problem with VACUUM FULL would be autovacuum waiting for an
> exclusive lock on the table.  Anyway, it is documented now as a possible
> issue.
> 
-- 
Command Prompt, Inc., Your PostgreSQL solutions company. 503-667-4564
Custom programming, 24x7 support, managed services, and hosting
Open Source Authors: plPHP, pgManage, Co-Authors: plPerlNG
Reliable replication, Mammoth Replicator - http://www.commandprompt.com/




view thread (19+ messages)  latest in thread

Message-ID: <1111792626.5783.11.camel@jd2.commandprompt.com>
Permalink:  ../1111792626.5783.11.camel@jd2.commandprompt.com/
Also on:    postgresql.org/message-id/1111792626.5783.11.camel@jd2.commandprompt.com

 · 

reply

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, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, matthew@zeut.net, o.blomqvist@secomintl.com
  Subject: Re: pg_autovacuum not having enough suction ?
  In-Reply-To: <1111792626.5783.11.camel@jd2.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