From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | michael(at)synchronicity(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: FATAL message on Linux |
Date: | 2003-07-29 16:06:35 |
Message-ID: | 22617.1059494795@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Brusser <michael(at)synchronicity(dot)com> writes:
> Now, (on Linux only) we sometimes run into this:
> 2003-07-29 11:31:15 [26665] LOG: smart shutdown request
> 2003-07-29 11:31:15 [26728] LOG: shutting down
> 2003-07-29 11:31:17 [26728] LOG: database system is shut down
> 2003-07-29 11:31:19 [26767] LOG: database system was shut down at
> 2003-07-29 11:31:17 EDT
> 2003-07-29 11:31:19 [26767] LOG: checkpoint record is at 0/C01520
> 2003-07-29 11:31:19 [26767] LOG: redo record is at 0/C01520; undo record
> is at 0/0; shutdown TRUE
> 2003-07-29 11:31:19 [26767] LOG: next transaction id: 15648; next oid:
> 18523
> 2003-07-29 11:31:24 [26769] FATAL: The database system is starting up
> 2003-07-29 11:31:26 [26767] LOG: database system is ready
This just looks like some client tried to connect before the startup
process finished. It'll get turned away with a message like the above.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-07-29 16:17:29 | Re: Make clean fails |
Previous Message | Andrew Dunstan | 2003-07-29 16:02:46 | Re: an aggregate array function |