AW: AW: more corruption

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tim Perdue <tperdue(at)valinux(dot)com>, pgsql-hackers(at)hub(dot)org
Subject: AW: AW: more corruption
Date: 2000-07-11 13:11:34
Message-ID: 11C1E6749A55D411A9670001FA687963367FEE@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> >>>> 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 ) but
> > not yet committed(t_xmin > CurrentTransactionId) tuples.
> > He will see them in the future.

Yes, good point. Is there a way to set CurrentTransactionId to a value
greater that the smallest t_xmin ?

>
> But he did a vacuum --- won't that get rid of any tuples that aren't
> currently considered committed?

He said that the vacuum was blocking and he thus killed it.
The vacuum was thus only partway done.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Bitmead 2000-07-11 13:20:28 Re: Storage Manager (was postgres 7.2 features.)
Previous Message Philip Warner 2000-07-11 13:10:25 Re: Patch for pg_dump