| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: How to reset WAL enveironment |
| Date: | 2000-12-07 20:34:17 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D31DF@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin A. Marques | 2000-12-07 20:34:54 | Re: v7.1 beta 1 ...packaged, finally ... |
| Previous Message | Tom Lane | 2000-12-07 20:28:42 | Re: beta testing version |