From: Robert Treat <xzilla@users.sourceforge.net>
To: pgsql-hackers@postgresql.org
Cc: Tom Lane <tgl@postgresql.org>
Subject: Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
Date: Thu, 27 Mar 2008 16:56:45 -0400
Message-ID: <200803271656.45574.xzilla@users.sourceforge.net> (raw)
In-Reply-To: <20080317021856.0D2D37558DC@cvs.postgresql.org>
References: <20080317021856.0D2D37558DC@cvs.postgresql.org>
On Sunday 16 March 2008 22:18, Tom Lane wrote:
> Log Message:
> -----------
> Fix TransactionIdIsCurrentTransactionId() to use binary search instead of
> linear search when checking child-transaction XIDs. This makes for an
> important speedup in transactions that have large numbers of children,
> as in a recent example from Craig Ringer. We can also get rid of an
> ugly kluge that represented lists of TransactionIds as lists of OIDs.
>
Are there any plans to backpatch this into REL8_3_STABLE? It looks like I am
hitting a pretty serious performance regression on 8.3 with a stored
procedure that grabs a pretty big recordset, and loops through doing
insert....update on unique failures. The procedure get progressivly slower
the more records involved... and dbx shows me stuck in
TransactionIdIsCurrentTransactionId(). I can provide provide more details if
needed (lmk what your looking for) but it certainly looks like the issue
discussed here:
http://archives.postgresql.org/pgsql-performance/2008-03/msg00191.php
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
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: xzilla@users.sourceforge.net, pgsql-hackers@postgresql.org, tgl@postgresql.org
Subject: Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
In-Reply-To: <200803271656.45574.xzilla@users.sourceforge.net>
* 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