Re: One tuple per transaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Richard Huxton <dev(at)archonet(dot)com>, Tambet Matiisen <t(dot)matiisen(at)aprote(dot)ee>, pgsql-performance(at)postgresql(dot)org
Subject: Re: One tuple per transaction
Date: 2005-03-15 23:51:19
Message-ID: 818.1110930679@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> On a similar note I was just wondering if it would be possible to
> mark any of these dead tuples as ready to be reused at transaction
> commit time, since we know that they are dead to any and all other
> transactions currently going on.

I believe VACUUM already knows that xmin = xmax implies the tuple
is dead to everyone.

> This would save you from having to vacuum to get the tuples marked
> ready for reuse.

No; you forgot about reclaiming associated index entries.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alvaro Herrera 2005-03-16 00:06:29 Re: One tuple per transaction
Previous Message Rod Taylor 2005-03-15 23:50:27 Re: Performance problem on delete from for 10k rows.