Re: [HACKERS] Another nasty cache problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Another nasty cache problem
Date
Msg-id 7988.949771109@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Another nasty cache problem  (Patrick Welche <prlw1@newn.cam.ac.uk>)
Responses Re: [HACKERS] Another nasty cache problem
List pgsql-hackers
Patrick Welche <prlw1@newn.cam.ac.uk> writes:
>> Is there anything in the postmaster log?

> DEBUG:  Data Base System is in production state at Fri Feb  4 17:11:05 2000
> Server process (pid 3588) exited with status 11 at Fri Feb  4 17:14:57 2000

> But no core file ... so who knows what the sigsegv comes from. (don't worry
> coredumpsize    unlimited)

There sure oughta be a corefile after a SIGSEGV.  Hmm.  How are you
starting the postmaster --- is it from a system startup script?
It might work better to start it from an ordinary user process.
I discovered the other day on a Linux box that the system just plain
would not dump a core file from a process started by root, even though
the process definitely had nonzero "ulimit -c" and had set its euid
to a nonprivileged userid.  But start the same process by hand from an
unprivileged login, and it would dump a core file.  Weird.  Dunno if
your platform behaves the same way, but it's worth trying.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Status of inheritance-changing patch
Next
From: Oleg Bartunov
Date:
Subject: Linux MANDRAKE startup startup script is broken ?