pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Gregory Stark <stark@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-patches@postgreSQL.org
Subject: Re: WIP patch for latestCompletedXid method of computing snapshot xmax
Date: Sat, 08 Sep 2007 02:48:26 +0100
Message-ID: <878x7i0vx1.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <3018.1189214811@sss.pgh.pa.us>
References: <3018.1189214811@sss.pgh.pa.us>

"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> This patch implements Florian's idea about how to manage snapshot xmax
> without the ugly and performance-losing tactic of taking XidGenLock and
> ProcArrayLock at the same time.  I had to do a couple of slightly klugy
> things to get bootstrap and prepared transactions to work, but on the
> whole it seems at least as clean as the code we have now.  Comments?

Just that it will be fascinating to see what effects this has on the
benchmarks.


-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com



view thread (17+ messages)  latest in thread

Message-ID: <878x7i0vx1.fsf@oxford.xeocode.com>
Permalink:  ../878x7i0vx1.fsf@oxford.xeocode.com/
Also on:    postgresql.org/message-id/878x7i0vx1.fsf@oxford.xeocode.com

 · 

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-hackers@postgresql.org
  Cc: stark@enterprisedb.com, tgl@sss.pgh.pa.us, pgsql-patches@postgreSQL.org
  Subject: Re: WIP patch for latestCompletedXid method of computing snapshot xmax
  In-Reply-To: <878x7i0vx1.fsf@oxford.xeocode.com>

* 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