From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PgSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: backend crash following load command |
Date: | 2006-11-28 20:14:22 |
Message-ID: | 20061128201422.GI29938@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Nov 28, 2006 at 02:38:18PM -0500, Merlin Moncure wrote:
> On 11/28/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >"Merlin Moncure" <mmoncure(at)gmail(dot)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(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Wm.A.Stafford | 2006-11-28 20:19:43 | using a sequence as the functional equivalent to Oracle rownum |
Previous Message | Ragnar | 2006-11-28 20:12:14 | Re: How to implement backup protocol |