Re: [HACKERS] JDBC behaviour

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com>, PostgreSQL-hackers <pgsql-hackers(at)postgresql(dot)org>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [HACKERS] JDBC behaviour
Date: 2016-02-23 13:34:17
Message-ID: CA+TgmoZBog10UOqTR2agtcm7SZ0jcYxwiKYESSiyOb6ZVqALMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-jdbc

On Sat, Feb 20, 2016 at 4:14 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> currently PostgreSQL::"set autocommit to FALSE ( not supported )
>
> This also does not make any sense.
>
> PgJDBC does support turning autocommit off. So I don't know in what way it's
> "not supported".

I believe Sridhar is imagining that someday "set autocommit to false"
might be a command that the server would understand.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2016-02-23 13:48:37 Re: JDBC behaviour
Previous Message Kaushal Shriyan 2016-02-23 13:24:56 Re: Select specific tables in BDR

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-02-23 13:36:46 Re: Speed up Clog Access by increasing CLOG buffers
Previous Message Robert Haas 2016-02-23 13:31:00 Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby

Browse pgsql-jdbc by date

  From Date Subject
Next Message Craig Ringer 2016-02-23 13:48:37 Re: JDBC behaviour
Previous Message Dave Cramer 2016-02-23 12:01:59 Re: JDBC behaviour