| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Bill Todd <pg(at)dbginc(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Nested transactions |
| Date: | 2009-10-13 00:08:19 |
| Message-ID: | 20091013000819.GC5954@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeff Davis escribió:
> On Mon, 2009-10-12 at 16:18 -0700, Bill Todd wrote:
> > Savepoints do not provide the same functionality as nested or parallel
> > transactions because you cannot commit a savepoint.
>
> What does it mean to "commit" a subtransaction or savepoint? What can
> you do with a subtransaction that you can't do with a savepoint?
What Bill wants is an "autonomous" transaction. We don't have those yet
(except thru use of dblink or database connections inside a function.)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Kortschak | 2009-10-13 00:14:59 | `must be superuser to COPY to or from a file' - using perl DBI - approaches to work around this |
| Previous Message | Jeff Davis | 2009-10-12 23:41:30 | Re: Nested transactions |