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

From Hiroshi Inoue
Subject RE: AW: more corruption
Date
Msg-id 000d01bfeaca$784144e0$2801007e@tpf.co.jp
Whole thread Raw
In response to Re: AW: more corruption  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: AW: more corruption  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Re: AW: more corruption  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> -----Original Message-----
> From: pgsql-hackers-owner@hub.org [mailto:pgsql-hackers-owner@hub.org]On
> Behalf Of Tom Lane
>
> 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.
>

Hmm,this may be more serious.
MVCC doesn't see committed(marked HEAP_XMIN_COMMITTED) but
not yet committed(t_xmin > CurrentTransactionId) tuples.
He will see them in the future.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp



pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: pg_backup symlink?
Next
From: Lamar Owen
Date:
Subject: Re: Distribution making