Re: FOR KEY LOCK foreign keys

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "noah" <noah(at)2ndquadrant(dot)com>,"dimitri" <dimitri(at)2ndquadrant(dot)fr>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FOR KEY LOCK foreign keys
Date: 2011-07-19 17:49:53
Message-ID: 4E257D71020000250003F4F6@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Kevin Grittner's message:
>> Noah Misch wrote:
>>
>>> With this patch in its final form, I have completed 180+ suite
>>> runs without a failure.
>>
>> The attached patch allows the tests to pass when
>> default_transaction_isolation is stricter than 'read committed'.
>> This is a slight change from the previously posted version of the
>> files (because of a change in the order of statements, based on
>> the timeouts), and in patch form this time.
>
> Thanks, applied. Sorry for the delay.

My patch was intended to supplement Noah's patch here:

http://archives.postgresql.org/pgsql-hackers/2011-07/msg00867.php

Without his patch, there is still random failure on my work machine
at all transaction isolation levels.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-07-19 18:07:22 Re: FOR KEY LOCK foreign keys
Previous Message Alvaro Herrera 2011-07-19 17:35:59 Re: Function argument names in pg_catalog