Re: [HACKERS] Another nasty cache problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: prlw1(at)cam(dot)ac(dot)uk
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Another nasty cache problem
Date: 2000-02-05 17:18:29
Message-ID: 7988.949771109@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2000-02-05 18:15:35 Linux MANDRAKE startup startup script is broken ?
Previous Message Tom Lane 2000-02-05 17:10:35 Status of inheritance-changing patch