From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Reuven M(dot) Lerner" <reuven(at)lerner(dot)co(dot)il> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Recovering a messed-up database |
Date: | 2007-05-15 00:12:42 |
Message-ID: | 1514.1179187962@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Reuven M. Lerner" <reuven(at)lerner(dot)co(dot)il> writes:
> To make a long story short, I thought that the site administrator was
> making regular backups, and that I was running pg_dump every night.
> Unfortunately, neither assumption was quite right. The administrator
> was using rsync to back things up, and accidentally reversed the
> parameters a few nights ago, thus wiping out the contents of our PGDATA
> directory. Well, not *all* of PGDATA. Among the things that were
> partly or completely saved are PGDATA/base. But PGDATA/global, as well
> as pg_clog, pg_xlog, and so forth are completely gone.
You're hosed :-(. Without pg_clog you can't trust any of the data
files, at least not for recently-modified data. If it's possible to
rebuild without depending on the files you have, I'd definitely counsel
going that way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dawid Kuroczko | 2007-05-15 04:33:26 | Performance issues of one vs. two split tables. |
Previous Message | Matthew Terenzio | 2007-05-15 00:04:04 | Re: Restarting postgres server |