| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: production server down |
| Date: | 2004-12-15 04:42:03 |
| Message-ID: | 26597.1103085723@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> I've got a down production server (will not restart) with the following
> tail to its log file:
Please show the output of pg_controldata, or a hex dump of pg_control
if pg_controldata fails.
> The server experienced a hang (as yet unexplained) yesterday and was
> restarted at 2004-12-13 16:38:49 according to syslog. I'm told by the
> network admin that there was a problem with the network card on restart,
> so the nfs mount most probably disappeared and then reappeared
> underneath a quiescent postgresql at some point between 2004-12-13
> 16:39:55 and 2004-12-14 15:36:20 (but much closer to the former than the
> latter).
I've always felt that running a database across NFS was a Bad Idea ;-)
> Any help would be much appreciated. Is our only option pg_resetxlog?
Possibly, but let's try to dig first. I suppose the DB is too large
to save an image aside for forensics later?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-12-15 05:14:06 | Re: production server down |
| Previous Message | Bruce Momjian | 2004-12-15 03:52:22 | libpq *.def files built for non-Win32 |