From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Tim Perdue'" <tperdue(at)valinux(dot)com> |
Cc: | pgsql-hackers(at)hub(dot)org |
Subject: | AW: AW: more corruption |
Date: | 2000-07-10 13:49:31 |
Message-ID: | 11C1E6749A55D411A9670001FA687963367FEC@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > > > -currently vacuuming the new db - nothing is barfing yet
> >
> > Actually, the vacuum seemed to be running forever making no
> > progress so
> > I killed it.
> >
> > > > > -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?
>
> Tuples that have been inserted/updated/deleted after last vacuum
> in old db assume that the corresponding txn has to be rolled back.
Correction: Tuples that have been inserted/updated/deleted but have not
been accessed afterwards (the magic first access that updates the tuple
transaction status inplace).
> Since your vacuum on old db only did half the db, that half
> will be current,
> but the rest will be old, thus you loose consistency.
>
> One of the core please confirm.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy J.M. Cain | 2000-07-10 13:52:21 | Re: Re: postgres TODO |
Previous Message | Karel Zak | 2000-07-10 13:43:41 | memory: bug or feature |