Re: One tuple per transaction - Mailing list pgsql-performance

From Tom Lane
Subject Re: One tuple per transaction
Date
Msg-id 818.1110930679@sss.pgh.pa.us
Whole thread Raw
In response to Re: One tuple per transaction  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: One tuple per transaction
List pgsql-performance
Robert Treat <xzilla@users.sourceforge.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

pgsql-performance by date:

Previous
From: Rod Taylor
Date:
Subject: Re: Performance problem on delete from for 10k rows.
Next
From: Alvaro Herrera
Date:
Subject: Re: One tuple per transaction