pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: marty@outputservices.com
Cc: herve@elma.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Sat, 22 Jan 2005 16:10:23 -0500
Message-ID: <25335.1106428223@sss.pgh.pa.us> (raw)
In-Reply-To: <20050122.121300.41631131.t-ishii@sra.co.jp>
References: <41F144FE.30902@outputservices.com>
	<41F14758.4030602@outputservices.com>
	<20050122.121300.41631131.t-ishii@sra.co.jp>

Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> Probably VACUUM works well for small to medium size tables, but not
> for huge ones. I'm considering about to implement "on the spot
> salvaging dead tuples".

That's impossible on its face, except for the special case where the
same transaction inserts and deletes a tuple.  In all other cases, the
transaction deleting a tuple cannot know whether it will commit.

			regards, tom lane



view thread (131+ messages)  latest in thread

Message-ID: <25335.1106428223@sss.pgh.pa.us>
Permalink:  ../25335.1106428223@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25335.1106428223@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-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, t-ishii@sra.co.jp, marty@outputservices.com, herve@elma.fr
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <25335.1106428223@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