Skip site navigation (1) Skip section navigation (2)

Re: TODO: Add a GUC to control whether BEGIN inside

From: "Jaime Casanova" <systemguards(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Lukas Kahwe Smith" <smith(at)pooteeweet(dot)org>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO: Add a GUC to control whether BEGIN inside
Date: 2007-01-04 01:42:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 1/2/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Lukas Kahwe Smith <smith(at)pooteeweet(dot)org> writes:
> > Err, I think you misunderstood what I said. My implementation uses
> > SAVEPOINTs already. The point is having some API where you do not have
> > to care of you are already in a transaction or not.
> It's not that hard, is it?
>        if (PQtransactionStatus(conn) == PQTRANS_IDLE)
>                PQexec(conn, "BEGIN");
>        else
>                PQexec(conn, "SAVEPOINT foo");
>                        regards, tom lane

and  how the releases and commit will happen? all at once or one by one?

Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
                                       Richard Cook

In response to

pgsql-hackers by date

Next:From: Euler Taveira de OliveiraDate: 2007-01-04 01:46:57
Subject: Re: xlog directory at initdb time
Previous:From: Andrew DunstanDate: 2007-01-04 01:05:27
Subject: Re: [HACKERS] Patch to log usage of temporary files

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group