Re: backend crash following load command - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: backend crash following load command
Date
Msg-id 20061128201422.GI29938@svana.org
Whole thread Raw
In response to Re: backend crash following load command  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: backend crash following load command  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Nov 28, 2006 at 02:38:18PM -0500, Merlin Moncure wrote:
> On 11/28/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >"Merlin Moncure" <mmoncure@gmail.com> writes:
> >> We are getting a backend crash after issueing a load command.
> >
> >No crash from your example here (on Fedora Core 5).  What platform and
> >gcc are you using exactly?  Can you provide a stack trace from the crash?
>
> ok, an update on this.  we actually covered up the bug in reducing the
> problem to our test case.  our make system used cp -f to overwite the
> .so file in use by postgresql.  interestingly, this will cause a crash
> on the .so reload via LOAD.  There may be a perfectly normal reason
> for this.

Err, that means copy is just rewriting the executable code in the
backend of the server, while it's running, which understandably
crashes. Probably while trying to unload the old library. I suppose the
answer is: don't do that.

The protection of ETXTBUSY only applies to code started via exec().

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: Tony Caduto
Date:
Subject: Re: Only MONO/WinForms is a way to go
Next
From: "Wm.A.Stafford"
Date:
Subject: using a sequence as the functional equivalent to Oracle rownum