pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
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 23:44:30 -0500
Message-ID: <2284.1110948270@sss.pgh.pa.us> (raw)
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>

Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> On Tue, Mar 15, 2005 at 06:51:19PM -0500, Tom Lane wrote:
>> 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?

Well, it's still correct as a fast-path check.  There are extensions
you could imagine making ... but offhand I agree that it's not worth
the trouble.  Maybe in a few years when everyone and his sister is
using subtransactions constantly, we'll feel a need to optimize these
cases. 

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <2284.1110948270@sss.pgh.pa.us>
Permalink:  ../2284.1110948270@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2284.1110948270@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, alvherre@dcc.uchile.cl, xzilla@users.sourceforge.net, dev@archonet.com, t.matiisen@aprote.ee
  Subject: Re: One tuple per transaction
  In-Reply-To: <2284.1110948270@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