Re: postmaster quits - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: postmaster quits
Date
Msg-id Pine.BSF.4.21.0108291132530.48187-100000@megazone23.bigpanda.com
Whole thread Raw
In response to postmaster quits  (Marc Prewitt <mprewitt@chelsea.net>)
List pgsql-bugs
> Please enter a FULL description of your problem:
> ------------------------------------------------
>
> Our development server, on occaision, runs out of swap space and
> inevitably when it does, the postmaster process stops.  When restarted,
> the following info is in the log (the machine ran out of swap around
> 19:17):
>
> DEBUG:  starting up
> DEBUG:  database system was interrupted at 2001-08-27 19:17:33
> DEBUG:  CheckPoint record at (0, 218748312)
> DEBUG:  Redo record at (0, 218748312); Undo record at (0, 0); Shutdown
> FALSE
> DEBUG:  NextTransactionId: 213780; NextOid: 297035
> DEBUG:  database system was not properly shut down; automatic recovery in
> progress...
> DEBUG:  ReadRecord: record with zero len at (0, 218748376)
> DEBUG:  Formatting logfile 0 seg 13 block 78 at offset 5592
> DEBUG:  The last logId/logSeg is (0, 13)
> DEBUG:  redo is not required
> DEBUG:  database system is in production state
>
> It is odd that postgresql doesn't create a core file or retry it's
> mallocs.  We are running mysql and Oracle on the same machine and neither
> of them have had this problem during the temporary memory shortage.

It looks like you've got the logs from restarting, but is there anything
from before that?  Also, if you're sure that a core didn't get created in
your database directory, you may need to make sure it's being started
with options that allow it to create a core (check the ulimit setting).

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Indices get ignored in large tables
Next
From: John Summerfield
Date:
Subject: A problem with WAL