| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Cassio Polpo de Campos <cassio(at)ime(dot)usp(dot)br> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Nested transactions |
| Date: | 2004-05-09 14:59:31 |
| Message-ID: | 20040509145931.GB2345@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 09, 2004 at 10:57:45AM -0300, Cassio Polpo de Campos wrote:
> I know nested transactions did not work on that versions, but this
> is exactly what I want to know. What happens if I put nested begins,
> commits, etc? Suppose we have the following:
>
> begin work
> ...
> begin work
> ...
> commit
> ...
> commit
You'll get a warning in the second begin saying that you already are in
a transaction, and nothing will happen. The first commit will commit,
and the second one will get another warning saying that you are not on a
transaction and there's nothing to commit.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Siempre hay que alimentar a los dioses, aunque la tierra esté seca" (Orual)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-05-09 16:09:49 | Re: Adding MERGE to the TODO list (resend with subject) |
| Previous Message | Peter Eisentraut | 2004-05-09 14:43:31 | Re: Relocatable installs |