From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How to reset WAL enveironment |
Date: | 2000-12-06 02:30:22 |
Message-ID: | 3A2DA4BE.F2255ED@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mikheev, Vadim wrote:
>
> > I see now the following message and couldn't start
> > postmaster.
> >
> > FATAL 2: btree_insert_redo: uninitialized page
> >
> > Is it a bug ?
>
> Seems so. btree_insert_redo shouldn't see uninitialized pages
> (only newroot and split ops add pages to index and they should
> be redone before insert op).
> Can you post/ftp me tgz of data dir?
> Or start up postmaster with --wal_debug=1 and send me
> output.
>
Probably this is caused by my trial (local) change
and generated an illegal log output.
However it seems to mean that WAL isn't always
redo-able. In my case the index is probably a
system index unfortunately. Is there a way to
avoid invoking recovery process at startup ?
Regards.
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Mikheev, Vadim | 2000-12-06 04:24:50 | RE: How to reset WAL enveironment |
Previous Message | Arno A. Karner | 2000-12-06 01:38:13 | shared libs on sco how? |