Re: BUG #9464: PANIC with 'failed to re-find shared lock object'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter LaDow <petela(at)gocougs(dot)wsu(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9464: PANIC with 'failed to re-find shared lock object'
Date: 2014-03-07 04:47:05
Message-ID: 1082.1394167625@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter LaDow <petela(at)gocougs(dot)wsu(dot)edu> writes:
> On Thu, Mar 6, 2014 at 8:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Could you try patching atexit_callback as above, and verify that
>> it does what you want (with or without the on_exit_reset() in your
>> extension)?

> That did it as well. Things are peachy (at least for this scenario).

> Would you like me to submit a patch (with you as the author of course)?

I think the right next step is to ask on pgsql-hackers if anyone can see
a flaw in this approach. I'll go do that. Thanks for following up!

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Wilfried.Weiss 2014-03-07 12:53:47 BUG #9472: pg_dumpall fails with "unrecognized node type: 650"
Previous Message Peter LaDow 2014-03-07 04:37:43 Re: BUG #9464: PANIC with 'failed to re-find shared lock object'