Re: BUG #5952: SetRWConflict assertion failure

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
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 15:18:39
Message-ID: 4D9AEC7F020000250003C307@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> This patch looks reasonable, but I'm a bit concerned about the
> chunk immediately preceding the patched area.
>
> When we do this:
>
> LWLockRelease(SerializableXactHashLock);
> LWLockRelease(partitionLock);
> LWLockRelease(SerializablePredicateLockListLock);
> LWLockAcquire(partitionLock, LW_SHARED);
> LWLockAcquire(SerializableXactHashLock, LW_SHARED);
>
> Don't we need to also reset nextpredlock to the head of the list?
> I'm assuming it's the partitionLock that's keeping the
> PREDICATELOCKs from bouncing out from under us, so if we release
> it, aren't we potentially point off into thin air?

I think you are right. That sequence should be followed by a copy
of the same "nextpredlock = " statement that's just above. Do you
want me to revise the patch or do you just want to take care of it
as part of the commit?

Thanks for catching that.

-Kevin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-04-05 15:29:59 Re: BUG #5952: SetRWConflict assertion failure
Previous Message Robert Haas 2011-04-05 14:56:51 Re: BUG #5952: SetRWConflict assertion failure