Re: SERIALIZABLE and INSERTs with multiple VALUES

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Jason Dusek <jason(dot)dusek(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: SERIALIZABLE and INSERTs with multiple VALUES
Date: 2016-10-11 20:00:03
Message-ID: CACjxUsP8Ff5ftB1WRHQwdx6v3ftjMHyvpBvoAANBvAtqx8r8ww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Oct 11, 2016 at 2:29 PM, Jason Dusek <jason(dot)dusek(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Richards 2016-10-11 20:06:19 Re: LOG: munmap(0x7fff80000000) failed: Invalid argument
Previous Message Chris Richards 2016-10-11 19:54:09 Re: LOG: munmap(0x7fff80000000) failed: Invalid argument