pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
Date: Mon, 21 Apr 2008 12:54:24 -0400
Message-ID: <20080421165424.GC14464@alvh.no-ip.org> (raw)
In-Reply-To: <200804211229.00871.xzilla@users.sourceforge.net>
References: <20080317021856.0D2D37558DC@cvs.postgresql.org>
	<200803271656.45574.xzilla@users.sourceforge.net>
	<2092.1206652297@sss.pgh.pa.us>
	<200804211229.00871.xzilla@users.sourceforge.net>

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.



view thread (13+ messages)  latest in thread

Message-ID: <20080421165424.GC14464@alvh.no-ip.org>
Permalink:  ../20080421165424.GC14464@alvh.no-ip.org/
Also on:    postgresql.org/message-id/20080421165424.GC14464@alvh.no-ip.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: alvherre@commandprompt.com, xzilla@users.sourceforge.net
  Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search
  In-Reply-To: <20080421165424.GC14464@alvh.no-ip.org>
  References: <20080317021856.0D2D37558DC@cvs.postgresql.org> <200803271656.45574.xzilla@users.sourceforge.net> <2092.1206652297@sss.pgh.pa.us> <200804211229.00871.xzilla@users.sourceforge.net> <20080421165424.GC14464@alvh.no-ip.org>

* 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