Re: BUG #3245: PANIC: failed to re-find shared lock object

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, "Dorochevsky, Michel" <michel(dot)dorochevsky(at)softcon(dot)de>, pgsql-bugs(at)postgresql(dot)org, Dave Page <dpage(at)postgresql(dot)org>
Subject: Re: BUG #3245: PANIC: failed to re-find shared lock object
Date: 2007-04-26 23:31:21
Message-ID: 28403.1177630281@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers pgsql-patches

I wrote:
> Also, we have a generic issue that making fresh entries in a hashtable
> might result in a concurrent hash_seq_search scan visiting existing
> entries more than once; that's definitely not something any of the
> existing callers are thinking about.

> I'm too tired to think about fixes right now, but we've definitely
> found a hotbed of actual and potential bugs.

I've committed a fix for this; it'll be in the next set of releases.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2007-04-27 01:07:24 Re: setseed accepts bad seeds
Previous Message Bruce Momjian 2007-04-26 22:45:40 Re: BUG #3048: pg_dump dumps intarray metadata incorrectly

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-04-26 23:36:36 Re: Implicit casts to text
Previous Message Bruce Momjian 2007-04-26 23:20:07 Re: Implicit casts to text

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-04-27 00:22:01 Re: Re: [HACKERS] [COMMITTERS] pgsql: Add GUC temp_tablespaces to provide a default location for
Previous Message Bruce Momjian 2007-04-26 23:09:57 Re: Preliminary GSSAPI Patches