Skip site navigation (1) Skip section navigation (2)

Re: production server down

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 06:32:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Joe Conway <mail(at)joeconway(dot)com> writes:
> Assuming the only real problem here is the control data (long shot, I 
> know), and the actual database files and transaction logs are OK, is 
> there any reasonable way to reconstruct the correct contol data? Or is 
> that the point at which you use pg_resetxlog?

Well, the problem is that if you can't trust pg_control you don't know
what you can trust.

My advice is to backup the $PGDATA tree (which you said was in
progress), then pg_resetxlog, then cross-check the hell out of the data
you see.  Only if you can detect some data problems can we guess at
something else to do ...

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Joe ConwayDate: 2004-12-15 07:07:51
Subject: Re: production server down
Previous:From: Joe ConwayDate: 2004-12-15 06:25:15
Subject: Re: production server down

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group