pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@dcc.uchile.cl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: Richard Huxton <dev@archonet.com>
Cc: Tambet Matiisen <t.matiisen@aprote.ee>
Cc: pgsql-performance@postgresql.org
Subject: Re: One tuple per transaction
Date: Tue, 15 Mar 2005 20:06:29 -0400
Message-ID: <20050316000629.GB17051@dcc.uchile.cl> (raw)
In-Reply-To: <818.1110930679@sss.pgh.pa.us>
References: <A66A11DBF5525341AEF6B8DE39CDE770088052@black.aprote.com>
	<4236ACE5.1040004@archonet.com>
	<200503151652.30266.xzilla@users.sourceforge.net>
	<818.1110930679@sss.pgh.pa.us>

On Tue, Mar 15, 2005 at 06:51:19PM -0500, Tom Lane wrote:
> 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.

Huh, that is too simplistic in a subtransactions' world, isn't it?

One way to solve this would be that a transaction that kills a tuple
checks whether it was created by itself (not necessarily the same Xid),
and somehow report it to the FSM right away.

That'd mean physically moving a lot of tuples in the page, so ISTM it's
too expensive an "optimization."  Oh, and also delete the tuple from
indexes.

-- 
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Vivir y dejar de vivir son soluciones imaginarias.
La existencia está en otra parte" (Andre Breton)



view thread (12+ messages)  latest in thread

Message-ID: <20050316000629.GB17051@dcc.uchile.cl>
Permalink:  ../20050316000629.GB17051@dcc.uchile.cl/
Also on:    postgresql.org/message-id/20050316000629.GB17051@dcc.uchile.cl

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: alvherre@dcc.uchile.cl, tgl@sss.pgh.pa.us, xzilla@users.sourceforge.net, dev@archonet.com, t.matiisen@aprote.ee
  Subject: Re: One tuple per transaction
  In-Reply-To: <20050316000629.GB17051@dcc.uchile.cl>
  References: <A66A11DBF5525341AEF6B8DE39CDE770088052@black.aprote.com> <4236ACE5.1040004@archonet.com> <200503151652.30266.xzilla@users.sourceforge.net> <818.1110930679@sss.pgh.pa.us> <20050316000629.GB17051@dcc.uchile.cl>

* 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