> 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.

> Anyway,how do I reset my WAL environment ?

Only one way - remove index file. I didn't add file node
to elog output yet (will do for beta2), but wal_debug
will show it.

Vadim

Tue, 5 Dec 2000 17:29:03 -0800 
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: How to reset WAL enveironment
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

Wed, 06 Dec 2000 11:30:22 +0900
Hiroshi Inoue <Inoue@tpf.co.jp>
Re: How to reset WAL enveironment