| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Named transaction |
| Date: | 2009-06-17 19:11:03 |
| Message-ID: | 20090617191103.GN6750@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark wrote:
> On Wed, Jun 17, 2009 at 6:40 PM, Alvaro
> Herrera<alvherre(at)commandprompt(dot)com> wrote:
> > AFAIK that's an "autonomous transaction", at least to some other RDBMSs.
>
> I have no idea what they are in Firebird but the name conjured up a
> different (interesting) idea for me. I had the image of naming a
> transaction and then being able to have other sessions join that same
> transaction. We've discussed this before for connection-pooled systems
> which want to be able to return their connection to the pool in the
> middle of their transaction.
Sounds a bit like a prepared transaction, except that you don't put it
aside for later commit but rather "suspend" it.
> It would also possibly be useful for parallel data dumps and loads.
I think the clone snapshot stuff would be more easily usable for that.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-06-17 19:38:19 | Re: Named transaction |
| Previous Message | Robert Haas | 2009-06-17 19:09:13 | Re: Named transaction |