I am not planning to allow subtransactions inside functions in my first
implementation, though it may be possible in the future.
---------------------------------------------------------------------------
Jean-Luc Lachance wrote:
> Yes Bruce,
>
> I was talking of a PL/PgSQL FOR <cursor> LOOP.
>
> I have a 15M row table that I have to scan to update from 3 tables as
> part of a routing process.
> It would be nice if I could commit a bunch of rows to reduce the memory
> and disk requirements, not to mention locks!
>
> Right now, updating with a LOOP takes as much resources as with a JOIN.
>
> JLL
>
>
> Bruce Momjian wrote:
> >
> > Jean-Luc Lachance wrote:
> > > Jon,
> > >
> > > What I would like to be able to do is within a loop for example, commit
> > > each iteration.
> >
> > You mean a PL/PgSQL for-loop? I was going to use command-counter to
> > separate out parts of a transaction for possible rollback, and a
> > PL/PgSQL for loop does not increment that counter.
> >
> > --
> > Bruce Momjian | http://candle.pha.pa.us
> > pgman@candle.pha.pa.us | (610) 359-1001
> > + If your life is a hard drive, | 13 Roberts Road
> > + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
