Re: A bad behavior under autocommit off mode - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: A bad behavior under autocommit off mode
Date
Msg-id Pine.LNX.4.44.0303211136510.2387-100000@peter.localdomain
Whole thread Raw
In response to Re: A bad behavior under autocommit off mode  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> That seems excessive.  There is a case for reporting autocommit (if
> we don't decide to remove it altogether, which is still an open
> argument).  I have not heard any complaints suggesting that we need any
> others.

If we don't remove autocommit altogether on the server-side, then this
whole exercise is nearly pointless, because it still won't allow a
noninteractive libpq application to go in, do PQexec("command") and quit.
Each such application would still have to either set the autocommit state
explicitly first or, the new proposal, query the autocommit status and
then issue a COMMIT or not, as needed.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: cursors: SCROLL default, error messages
Next
From: Peter Eisentraut
Date:
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign