Re: [HACKERS] Statement-level rollback - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: [HACKERS] Statement-level rollback
Date
Msg-id CAB=Je-EObnHpkGpRvHGw9QFhkeEFrkETjKtfUj5jA+dk9ZsPsg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Statement-level rollback  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
List pgsql-hackers
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.vladimir@gmail.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

pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: Re: [HACKERS] Logical replication existing data copy
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Bizarre choice of case for RELKIND_PARTITIONED_TABLE