AW: AW: more corruption

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:27:13
Message-ID: 11C1E6749A55D411A9670001FA687963367FE9@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Zeugswetter Andreas SB wrote:
> > > > -I created a new db
> > > > -used the old db schema to create all new blank tables
> >
> > vacuum new db
> > (I would do a tar backup of the whole old db)
> > vacuum old db, if that is possible
>
> Was not possible.
>
> > > > -copied the physical table files from the old data
> > > directory into the
> > > > new database directory
> >
> > if above vacuum old db was not possible copy old pg_log
>
> Oops - I didn't do that.
>
> > > > -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.
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-07-10 13:27:51 Re: postmaster errors with index on temp table?
Previous Message Bruce Momjian 2000-07-10 13:25:51 Re: Re: postgres TODO