| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Boes <jboes(at)nexcerpt(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Shared memory corrupted? |
| Date: | 2003-10-30 17:52:36 |
| Message-ID: | 1321.1067536356@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Jeff Boes <jboes(at)nexcerpt(dot)com> writes:
> Tom Lane wrote:
>> What's signal 14 on your machine? (Look in /usr/include/signal.h to
>> be sure.) Also, what PG version is this?
> 14) SIGALRM
> This is Pg 7.3.4, running on Linux 7.3 (Kernel 2.4.18-18.7.xsmp on a
> 2-processor i686).
Hm. That doesn't make any sense at all, because SIGALRM is either
caught by a handler or ignored everywhere in the Postgres backend.
There is no situation where it could legitimately cause process
termination. Is it possible you are dealing with a kernel bug?
[ thinks... ] Another possibility is that you are running some
non-Postgres code that resets SIGALRM handling to default. I have
heard rumors that Perl will do that in some cases, for example.
Are you using plperl?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Boes | 2003-10-30 18:04:17 | Re: Shared memory corrupted? |
| Previous Message | CLeon | 2003-10-30 17:28:10 | Re: [linux-lvm] RE: [PERFORM] backup/restore - another |