Re: SERIALIZABLE and INSERTs with multiple VALUES - Mailing list pgsql-general

From Kevin Grittner
Subject Re: SERIALIZABLE and INSERTs with multiple VALUES
Date
Msg-id CACjxUsP8Ff5ftB1WRHQwdx6v3ftjMHyvpBvoAANBvAtqx8r8ww@mail.gmail.com
Whole thread Raw
In response to SERIALIZABLE and INSERTs with multiple VALUES  (Jason Dusek <jason.dusek@gmail.com>)
Responses Re: SERIALIZABLE and INSERTs with multiple VALUES  (Jason Dusek <jason.dusek@gmail.com>)
Re: SERIALIZABLE and INSERTs with multiple VALUES  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-general
On Tue, Oct 11, 2016 at 2:29 PM, Jason Dusek <jason.dusek@gmail.com> 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


pgsql-general by date:

Previous
From: Chris Richards
Date:
Subject: Re: LOG: munmap(0x7fff80000000) failed: Invalid argument
Next
From: Chris Richards
Date:
Subject: Re: LOG: munmap(0x7fff80000000) failed: Invalid argument