> > > 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. > > > > Illegal log output is like disk crash - only BAR can help. > > But redo-recovery after restore would also fail. > The operation which corresponds to the illegal > log output aborted at the execution time and > rolling back by redo also failed. It seems > preferable to me that the transaction is rolled > back by undo. What exactly did you change in code? What kind of illegal log output? Was something breaking btree/WAL logic written to log? Vadim

Reply via email to