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

From Patrick Welche
Subject Re: [HACKERS] Another nasty cache problem
Date
Msg-id 20000205143515.F3402@quartz.newn.cam.ac.uk
Whole thread Raw
In response to Re: [HACKERS] Another nasty cache problem  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Another nasty cache problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Feb 04, 2000 at 03:58:57PM -0500, Tom Lane wrote:
> 
> > Any thoughts on where to look?
> 
> 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
Terminating any active server processes...
Server processes were terminated at Fri Feb  4 17:14:57 2000
Reinitializing shared memory and semaphores

>  Is there a core file (look
> in the database subdirectory, ie .../data/base/yourdatabase/core)?

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


> If so, compiling the backend with -g and extracting a backtrace from
> the resulting corefile with gdb would be very useful info.

(already have the -g..)

Still looking...

Cheers,

Patrick


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: [SQL] Re: [HACKERS] Proposed Changes to PostgreSQL
Next
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] Patch attached...