Re: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search - Mailing list pgsql-performance

From Alvaro Herrera
Subject Re: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
Date
Msg-id 20080421165424.GC14464@alvh.no-ip.org
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-performance
Robert Treat wrote:

> Unfortunatly I don't have the 8.1 system to bang on anymore for this, (though
> anecdotaly speaking, I never saw this behavior in 8.1) however I do now have
> a parallel 8.3 system crunching the data, and it is showing the same symptom
> (yes, 2 8.3 servers, crunching the same data, both bogged down now), so I do
> feel this is something specific to 8.3.
>
> I am mostly wondering if anyone else has encountered behavior like this on 8.3
> (large sets of insert....update exception block in plpgsql bogging down), or
> if anyone has any thoughts on which direction I should poke at it from here.
> TIA.

Perhaps what you could do is backpatch the change and see if the problem
goes away.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-performance by date:

Previous
From: Robert Treat
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
Next
From: PFC
Date:
Subject: Re: Group by more efficient than distinct?