| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "news(dot)postgresql(dot)org" <smith(at)pooteeweet(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: TODO: Add a GUC to control whether BEGIN inside |
| Date: | 2007-01-02 16:42:36 |
| Message-ID: | 20070102164236.GC21867@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
news.postgresql.org wrote:
> While we are on the topic, I have implemented a poor mans nested
> transaction feature into my database access layer. essentially
> subsequent calls to begin a transaction after the initial begin simply
> increase an internal counter and set a savepoint. as you commit the
> transactions the counter is decreased and the savepoints are released.
> maybe this could be implemented inside postgresql to make the life of
> modular programmers easier?
Yeah, it's called "SAVEPOINT foo" and "RELEASE foo".
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Kahwe Smith | 2007-01-02 16:48:15 | Re: TODO: Add a GUC to control whether BEGIN inside |
| Previous Message | news.postgresql.org | 2007-01-02 16:34:05 | Re: TODO: Add a GUC to control whether BEGIN inside |