Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
Date: 2008-03-28 05:55:56
Message-ID: 25149.1206683756@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers pgsql-performance

Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
>> If you can convince me it's a regression I might reconsider, but I
>> rather doubt that 8.2 was better,

> Well, I can't speak for 8.2, but I have a second system crunching the same
> data using the same function on 8.1 (on lesser hardware in fact), and it
> doesn't have these type of issues.

If you can condense it to a test case that is worse on 8.3 than 8.1,
I'm willing to listen...

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-03-28 15:00:28 pgsql: Clarify documentation on PITR and warm standby on the fact that
Previous Message Robert Treat 2008-03-28 05:51:54 Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2008-03-28 06:26:46 Re: PostgreSQL Replication with read-only access to standby DB
Previous Message Robert Treat 2008-03-28 05:51:54 Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search

Browse pgsql-performance by date

  From Date Subject
Next Message Vinubalaji Gopal 2008-03-28 07:28:33 Re: vacuum in Postgresql 8.0.x slowing down the database
Previous Message Robert Treat 2008-03-28 05:51:54 Re: [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search