Re: [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Ian Jackson <ian(dot)jackson(at)eu(dot)citrix(dot)com>
Cc: xen-devel(at)lists(dot)xenproject(dot)org, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation
Date: 2016-12-12 19:06:23
Message-ID: CACjxUsNKtNVhX6EoxY9FjS7N1aJ=inopGT0EqV_yKF6oup0p_g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Mon, Dec 12, 2016 at 12:32 PM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:

> As you can see, this generated a serialization failure.

That was on 9.6. On earlier versions it does indeed allow the
transaction on connection 2 to commit, yielding a non-serializable
result. This makes a pretty strong case for back-patching this
commit:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=fcff8a575198478023ada8a48e13b50f70054766

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-12-12 19:30:02 Re: tuplesort_gettuple_common() and *should_free argument
Previous Message Robert Haas 2016-12-12 18:49:26 Re: Typo in doc/src/sgml/catalogs.sgml