| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Andrew M(dot) Danneffel" <adanneffel(at)atomation(dot)ca> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Control File Context is Broken |
| Date: | 2002-01-12 06:56:00 |
| Message-ID: | 5223.1010818560@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Andrew M. Danneffel" <adanneffel(at)atomation(dot)ca> writes:
> The server is a
> cobalt RaQ4 running Red Hat Linux.
A version number for Postgres would be the useful tidbit here.
> 020111.16:00:01.144 [7651] FATAL 2: Control file context is broken
This error indicates that one of three fields in pg_control has a bogus
value. The only failures hereabouts that we've heard reported from the
field involve a silly timestamp. Is it possible that the system clock
was set to a silly value (ie, < 1970) last time you shut down? If so,
you could recover by commenting out the relevant check in
src/backend/access/transam/xlog.c.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | nn nn | 2002-01-12 21:55:14 | not recognized by setlocale() |
| Previous Message | Andrew M. Danneffel | 2002-01-12 05:55:49 | Control File Context is Broken |