Re: BUG #5952: SetRWConflict assertion failure

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: drkp(at)csail(dot)mit(dot)edu, yamt(at)mwd(dot)biglobe(dot)ne(dot)jp, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5952: SetRWConflict assertion failure
Date: 2011-04-05 19:17:48
Message-ID: BANLkTinX5ixT5uyTX6uCH+=59LJdg+2Qhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Apr 5, 2011 at 12:13 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> I wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>>> If you could send a revised patch, that would be great.
>>
>> Attached.  I put it in the same spot relative to the lock
>> acquisition that was used earlier in the function.
>
> And version 3 which might actually work.  [sigh]

Committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Joseph Adams 2011-04-05 20:31:35 Re: BUG #5963: make -j4 check fails
Previous Message Kevin Grittner 2011-04-05 16:13:35 Re: BUG #5952: SetRWConflict assertion failure