| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-21 17:29:58 | Re: makesign() broken in tsearch2 |
| Previous Message | Alvaro Herrera | 2006-01-21 15:48:05 | Re: Commands per transaction |