| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Add psql option: -1 or --single-transaction |
| Date: | 2006-02-14 16:48:48 |
| Message-ID: | 17540.1139935728@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> [It's a shame we don't support nested BEGINs, for use in nested function
> calls. I guess we took that out infavour of SAVEPOINTs? I seem to
> remember some idiot (me wasn't it?) suggesting we should do that.]
I still think that was probably the right move, though. With nested
BEGIN/COMMIT it'd be way too easy to get confused about how many levels
deep you are. The savepoint syntax at least provides names for the
levels. (Not that we have any mechanism to expose the state to you :-()
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-14 17:20:02 | pgsql: Move btbulkdelete's vacuum_delay_point() call to a place in the |
| Previous Message | Tom Lane | 2006-02-14 16:39:37 | pgsql: Add some missing vacuum_delay_point calls in GIST vacuuming. |