From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
---|---|
To: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC behaviour |
Date: | 2016-02-18 08:30:49 |
Message-ID: | CAB=Je-Haw2fcmXp53gx78DF7noP5neVzuaddJYm0TWMnUevG1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
> but in this case all these transactions are independent with autocommit off,
At database level, there is no "autocommit=off".
There's just "begin-end".
It is database who forbids .commit, not the JDBC driver.
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Sridhar N Bamandlapally | 2016-02-18 08:51:47 | Re: JDBC behaviour |
Previous Message | Andreas Joseph Krogh | 2016-02-18 08:30:27 | Re: JDBC behaviour |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-02-18 08:33:13 | Re: pg_ctl promote wait |
Previous Message | Andreas Joseph Krogh | 2016-02-18 08:30:27 | Re: JDBC behaviour |
From | Date | Subject | |
---|---|---|---|
Next Message | Sridhar N Bamandlapally | 2016-02-18 08:51:47 | Re: JDBC behaviour |
Previous Message | Andreas Joseph Krogh | 2016-02-18 08:30:27 | Re: JDBC behaviour |