> > No. I just started up postmaster with -S (logs are forwarded to syslog
> > in my settings).
>
> Oh. XLOG_DEBUG calls write(2,) - too big output for syslog I think.
I see. Next time I will turn off -S so that I could send you
XLOG_DEBUG outputs...
--
Tatsuo Ishii
> > Did you turn XLOG_DEBUG off?
> > With XLOG_DEBUG on there should be lines in log like
> >
> > REDO @ 0/434100; LSN 0/434252: .
> >
> > before control would reach btree_redo...
>
> No. I just started up postmaster with -S (logs are forwarded to syslog
> in my settings).
Oh. XLOG_DEB
> Did you turn XLOG_DEBUG off?
> With XLOG_DEBUG on there should be lines in log like
>
> REDO @ 0/434100; LSN 0/434252: .
>
> before control would reach btree_redo...
No. I just started up postmaster with -S (logs are forwarded to syslog
in my settings).
> Ok, anyway btree_xlog_delete
Did you turn XLOG_DEBUG off?
With XLOG_DEBUG on there should be lines in log like
REDO @ 0/434100; LSN 0/434252: .
before control would reach btree_redo...
Ok, anyway btree_xlog_delete is fixed. Thanks, Tatsuo!
And please try again -:)
Vadim
> It seems postmaster won't restart under W
It seems postmaster won't restart under WAL. What I have done so far
was creating some tables and inserting fairly large amount of tuples
(10 tuples) using pgbench.
Here is the test sequence:
pg_ctl -w stop
rm -fr /usr/local/pgsql/data
initdb
pg_ctl -w start
createdb test
./pgbench -i test
p
