| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Bill Todd <pg(at)dbginc(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Nested transactions |
| Date: | 2009-10-13 05:11:42 |
| Message-ID: | dcc563d10910122211g7750a340y7a7b6d134e276bc@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Oct 12, 2009 at 5:18 PM, Bill Todd <pg(at)dbginc(dot)com> wrote:
> Scott Marlowe wrote:
>
> On Sun, Oct 11, 2009 at 8:41 PM, Bill Todd <pg(at)dbginc(dot)com> wrote:
>
>
> Does PostgreSQL support nested transactions as shown below?
>
> BEGIN;
> ...do some stuff...
> BEGIN;
> ...more stuff...
> COMMIT;
> COMMIT;
>
>
> Postgresql uses savepoints.
>
>
>
>
> Savepoints do not provide the same functionality as nested
Yes they do. There was a REALLY long discussion on the subject in the
hackers list I believe that led to pgsql supporting savepoints but
not nested transactions
> or parallel transactions
That's something entirely different and a question you did not ask
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2009-10-13 05:30:15 | Re: Are there only 4 weights in PostgreSQL fulltext search? |
| Previous Message | Mitesh51 | 2009-10-13 05:03:13 | WAL handling issue. |