From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: production server down |
Date: | 2004-12-15 19:41:02 |
Message-ID: | 41C0934E.8000300@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Yes, override everything there's a switch for. Also check that the
> other values shown by pg_controldata look reasonable (the locale
> settings are probably the only ones you might get burned on).
>
>
>>>What if anything have you got in $PGDATA/pg_xlog?
>>
>>-rw------- 1 postgres postgres 16777216 Dec 13 15:39 0000016500000077
>
> Um. That's so far from the values shown in pg_control that it's not funny.
>
> This is 7.4, right? I have a crude xlog dump tool that I'll send you
> off-list. We should be able to identify the latest checkpoint in the
> existing XLOG files, and that will give you something to work with.
>
Just wanted to close the loop for the sake of the list archives. With
Tom's xlog dump tool I was able (with a bunch of his help off-list) to
identify the needed parameters for pg_resetxlog. Running pg_resetxlog
got us back a running database. We're now involved in checking the data.
Thank you to everyone for your help -- especially Tom!
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2004-12-15 20:46:28 | Identifying time of last stat reset via sql |
Previous Message | Matthias Schmidt | 2004-12-15 19:40:18 | Re: somebody working on: Prevent default re-use of sysids for dropped users and groups? |