Re: [HACKERS] Statement-level rollback

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [HACKERS] Statement-level rollback
Date: 2017-03-07 22:31:26
Message-ID: CAB=Je-EObnHpkGpRvHGw9QFhkeEFrkETjKtfUj5jA+dk9ZsPsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Please disregard my previous message.
pgjdbc is already doing upcase conversion, so I would like to see a test
case that reproduces the error.

Alternatively, could you please capture and share TRACE log? (
https://jdbc.postgresql.org/documentation/head/logging.html#configuration )

Vladimir

ср, 8 мар. 2017 г. в 1:26, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>:

> legrand>when usingversion 42.0.0 with
> legrand> jdbc:postgresql://localhost:5432/postgres?autosave=always
>
> The pitfall there is the value should be written with upper case like
> autosave=ALWAYS.
>
> I've filed https://github.com/pgjdbc/pgjdbc/issues/769 to improve that at
> some point.
>
>
> Vladimir
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-03-07 23:03:38 Re: Bizarre choice of case for RELKIND_PARTITIONED_TABLE
Previous Message Erik Rijkers 2017-03-07 22:30:50 Re: Logical replication existing data copy

Browse pgsql-jdbc by date

  From Date Subject
Next Message legrand legrand 2017-03-08 00:02:48 Re: Statement-level rollback
Previous Message Vladimir Sitnikov 2017-03-07 22:26:49 Re: Statement-level rollback