From: wieck@debis.com
To: maillist@candle.pha.pa.us
Cc: jwieck@debis.com
Cc: tgl@sss.pgh.pa.us
Cc: bkruger@mindspring.com
Cc: pgsql-admin@postgreSQL.org
Cc: pgsql-general@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [ADMIN] Re: [SQL] Data recovery
Date: Tue, 1 Jun 1999 21:01:39 +0200 (MET DST)
Message-ID: <m10otn9-0003kGC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <199906011728.NAA01606@candle.pha.pa.us>
>
> > > If you only have the data/base subdirectory, you will need to work
> > > harder; you'll have to regenerate the top-level files. I think if you
> > > get pg_shadow and pg_database right you will be OK. First, install and
> > > initdb to get a basic set of files. You will need to recall the old set
> > > of users (including their userIDs) in order to reconstruct pg_shadow.
> > > After you've done the createusers, issue a createdb for each old
> > > database (subdirectory of base/) so that they have entries in
> > > pg_database. Then, shut down the postmaster, blow away the contents of
> > > the base/ subdirectory and restore it from tape, and restart. I think
> > > it'll work...
> > >
> > > In any case it's critical to install the same Postgres version you
> > > were using.
> >
> > NO - this cannot work. He surely needs the entire data
> > directory because the information in the heap's relies on the
> > bits in data/pg_log. And that info (which XID's are
> > committed and which not) cannot be reconstructed from the
> > files - no chance.
>
> Very, very hard, but not impossible. If you update a row, and do a
> select on that row, the select updates the transaction status so the
> next select doesn't need to look at the pg_log table. What this means
> is that pg_log could probably be reconstructed from existing data, with
> just 'unselected' changes not appearing properly.
So at the end you have some data that you cannot trust. I
don't think that's worth the efford.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck@debis.com (Jan Wieck) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: wieck@debis.com, maillist@candle.pha.pa.us, jwieck@debis.com, tgl@sss.pgh.pa.us, bkruger@mindspring.com, pgsql-admin@postgreSQL.org, pgsql-general@postgreSQL.org
Subject: Re: [ADMIN] Re: [SQL] Data recovery
In-Reply-To: <m10otn9-0003kGC@orion.SAPserv.Hamburg.dsh.de>
References: <199906011728.NAA01606@candle.pha.pa.us> <m10otn9-0003kGC@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox