Skip site navigation (1) Skip section navigation (2)

Re: Commands per transaction

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commands per transaction
Date: 2006-01-21 16:37:15
Message-ID: 1137861435.53224.27.camel@home (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, 2006-01-21 at 12:48 -0300, Alvaro Herrera wrote:
> Rod Taylor wrote:
> > Is there any way of bumping this limit or am I stuck breaking up the
> > transaction?
> 
> Wow, I never heard of anyone reaching the limit :-(  Sorry, you are
> stuck (short of changing CommandId to 64 bits, which would bloat your
> tables considerably ...)

It was a complex plpgsql function iterating through a large volume of
data. It would appear that each IF statement in plpgsql is taken as a
separate statement because I don't believe I was dealing with more than
about 1.2B rows in a FOR ... EXECUTE 'SELECT ...' loop.


-- 


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-01-21 17:29:58
Subject: Re: makesign() broken in tsearch2
Previous:From: Alvaro HerreraDate: 2006-01-21 15:48:05
Subject: Re: Commands per transaction

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group