From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Date: Fri, 21 Mar 2003 13:06:24 -0500 (EST)
Message-ID: <200303211806.h2LI6OS20341@candle.pha.pa.us> (raw)
In-Reply-To: <14166.1048269607@sss.pgh.pa.us>
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > But isn't that like saying that the spec doesn't apply to libpq at all.
> > Why would autocommit not apply but other queries specification apply?
>
> No, you're missing the point. Essentially all the client libraries
> offer their own autocommit behavior on top of what the spec says.
Well, which ones? jdbc (which prevers the server autocommit), ecpg,
odbc (?), and Perl. Anyone else?
> libpq is alone in not having any such client-side logic. So it's not
> a foregone conclusion that we should implement autocommit on/off logic
> on the server side as a substitute for adding it to libpq. We have
> now tried doing it on the server side, and we are finding that we don't
> like the side-effects; so it's time to revisit that decision.
My concern is bloating the API for all languages based on libpq, and
psql and stuff like that. Heck, even pgadmin would have to have a
button for it because a SET couldn't control it.
I know the server-side isn't optimal, but is the alternative worse?
Also, if Peter wants clients to be able to just issue a query and know
it commits, should we just disable setting autocommit in postgresql.conf
and per-user/db, and force applications to turn it on explicitly?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, peter_e@gmx.net, alvherre@dcc.uchile.cl, pgsql-hackers@postgresql.org
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
In-Reply-To: <200303211806.h2LI6OS20341@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox