Re: PostgreSQL clustering VS MySQL clustering

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: marty(at)outputservices(dot)com, herve(at)elma(dot)fr, pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: 2005-01-24 02:52:44
Message-ID: 20050124.115244.35008937.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)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.

Of course. We need to keep a list of such that tuples until commit or
abort.
--
Tatsuo Ishii

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message SpaceBallOne 2005-01-24 07:56:41 poor performance of db?
Previous Message Hannu Krosing 2005-01-24 01:56:25 Re: PostgreSQL clustering VS MySQL clustering