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

From: Peter LaDow <petela(at)gocougs(dot)wsu(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:37:43
Message-ID: CAN8Q1EcvWGUTGe2DFGnDvWhgQmF63Vwib-RUHjUBXTEH61FMyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Mar 6, 2014 at 8:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I don't think _exit() is a terribly good idea. Consider the possibility
> that some third-party library loaded into the backend has also established
> an atexit callback, and unlike what we did, that code does need to get
> control in a subprocess exit.

Good point.

> 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)?

Thanks,
Pete

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-03-07 04:47:05 Re: BUG #9464: PANIC with 'failed to re-find shared lock object'
Previous Message Tom Lane 2014-03-07 04:18:16 Re: BUG #9464: PANIC with 'failed to re-find shared lock object'