Re: [HACKERS] JDBC behaviour - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [HACKERS] JDBC behaviour
Date
Msg-id CAMsr+YGsgSCE-jzVZY47ufW5ZXz8TRW42NKZtkHQ39s4P2PExQ@mail.gmail.com
Whole thread Raw
In response to Re: [JDBC] JDBC behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 23 February 2016 at 22:46, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Craig Ringer <craig@2ndquadrant.com> writes:
> On 23 February 2016 at 21:34, Robert Haas <robertmhaas@gmail.com> wrote:
>> I believe Sridhar is imagining that someday "set autocommit to false"
>> might be a command that the server would understand.

> ... I guess. Yeah.

We've been there, we've done that.  We're not doing it again.

Thanks for the pointer to the history.

I had zero enthusiasm for going that way anyway and was mostly trying to figure out what Sridhar was talking about. It's useful to know it's already been explored though.

I think we know where we need to go from here - updating that PgJDBC patch to add a connection option, making sure it doesn't add round-trips, adding tests and merging it. At this point it's up to Sridhar to start putting time and development effort into it to push it forward if desired.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Why vacuum_freeze_table_age etc. doc in "Statement Behavior" section?
Next
From: Michael Paquier
Date:
Subject: Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby