SELECT version(),
(SELECT setting FROM pg_settings WHERE name =
'default_transaction_deferrable') AS default_transaction_deferrable,
(SELECT setting FROM pg_settings WHERE name =
'default_transaction_isolation') AS default_transaction_isolation;
─[ RECORD 1
]──────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────────────────
version │ PostgreSQL 9.5.4 on
x86_64-apple-darwin15.6.0, compiled by Apple LLVM version 8.0.0
(clang-800.0.38), 64-bit
default_transaction_deferrable │ on
default_transaction_isolation │ serializable
On Tue, 11 Oct 2016 at 13:00 Kevin Grittner <[email protected]> wrote:
> On Tue, Oct 11, 2016 at 2:29 PM, Jason Dusek <[email protected]>
> wrote:
>
> > I notice the following oddity:
>
> > =# CREATE TABLE with_pk (i integer PRIMARY KEY);
> > CREATE TABLE
>
> > =# BEGIN;
> > BEGIN
> > =# INSERT INTO with_pk VALUES (2), (2) ON CONFLICT DO NOTHING;
> > ERROR: could not serialize access due to concurrent update
> > =# END;
> > ROLLBACK
>
> I don't see that on development HEAD. What version are you
> running? What is your setting for default_transaction_isolation?
>
> --
> Kevin Grittner
> EDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
