| From: | Jean-Luc Lachance <jllachan(at)nsd(dot)ca> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Jon Swinth <jswinth(at)atomicpc(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Two features left |
| Date: | 2002-11-28 15:49:35 |
| Message-ID: | 3DE63B0F.A28E82EC@nsd.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Luc Lachance | 2002-11-28 15:59:00 | Re: Two features left |
| Previous Message | jerome | 2002-11-28 15:27:03 | Incremental backup? |