Re: AW: more corruption - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: more corruption
Date
Msg-id 747.963242266@sss.pgh.pa.us
Whole thread Raw
In response to Re: AW: more corruption  (Tim Perdue <tperdue@valinux.com>)
Responses RE: AW: more corruption  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
Tim Perdue <tperdue@valinux.com> writes:
>>>>>> -now hopefully I can create my indexes and be back in business

> I vacuumed here and it worked. I did not use my "old" pg_log file - what
> did I lose?

Hard to tell.  Any tuples that weren't already marked on disk as "known
committed" have probably gone missing, because their originating
transaction IDs likely won't be shown as committed in the new pg_log.
So I'd look for missing tuples from recent transactions in the old DB.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: postgres TODO
Next
From: JanWieck@t-online.de (Jan Wieck)
Date:
Subject: Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...