pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mikko Partio <mpartio@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum full crash
Date: Sun, 30 Mar 2008 15:28:25 -0400
Message-ID: <27266.1206905305@sss.pgh.pa.us> (raw)
In-Reply-To: <2ca799770803301126p6facf429r108b06ca4e54440a@mail.gmail.com>
References: <2ca799770803291340p75d8a4e2o7dfd6c61e73270f6@mail.gmail.com>
	<21772.1206824718@sss.pgh.pa.us>
	<2ca799770803300356r185b1adbv2ab17c7cc8f212a7@mail.gmail.com>
	<10439.1206891635@sss.pgh.pa.us>
	<2ca799770803301126p6facf429r108b06ca4e54440a@mail.gmail.com>

"Mikko Partio" <mpartio@gmail.com> writes:
> Interesting. What is planned substitute for VACUUM FULL? CLUSTER?

What's been discussed is something that works roughly like CLUSTER
but doesn't bother to sort the data any particular way (ie, just do
a seqscan not an indexscan in the data-copying phase).  This would
certainly dominate VACUUM FULL in contexts where you've removed a
large fraction of the rows.  In cases where you haven't, the large
transient space requirement (2x the table size) would be objectionable,
but it's not real clear why you need a VACUUM FULL rather than plain
VACUUM in such cases anyway.

A lot of the context for this arises from recent and planned
improvements, notably

(1) CLUSTER is MVCC-safe now, removing one of the core arguments
for not using it for routine cleanup.

(2) Planned fixes like the dead space map will substantially
reduce the cost of running frequent plain vacuums.  That together
with autovacuum (which we could make more aggressive in consequence)
should help to avoid getting into situations where VACUUM FULL is
needed in the first place.

We certainly couldn't have considered eliminating VACUUM FULL before
this, but it's starting to seem a viable option to me.

			regards, tom lane



view thread (6+ messages)

Message-ID: <27266.1206905305@sss.pgh.pa.us>
Permalink:  ../27266.1206905305@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27266.1206905305@sss.pgh.pa.us

 · 

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mpartio@gmail.com
  Subject: Re: Vacuum full crash
  In-Reply-To: <27266.1206905305@sss.pgh.pa.us>

* 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