| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "'Alfred Perlstein'" <bright(at)wintelcom(dot)net>, The Hermit Hacker <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: Idea for reducing planning time |
| Date: | 2000-12-15 20:21:03 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D31FD@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Sorry guys, I'm busy with WAL issues currently.
> > CRC will require initdb, so it's better to implement it
> > first...
> > Also, is TOAST-table vacuuming fixed now?
>
> Can someone please remind me? CRC allows us to know of WAL log is
> corrupt?
Currently WAL has no means to know is log data consistent or not.
Eg - it may try to redo insertion of tuple which data were only
partially writtent to log disk pages (when record crosses page
boundary).
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-12-15 20:41:54 | Re: 7.1 (current) unwanted NOT NULL constraint inserted |
| Previous Message | Bruce Momjian | 2000-12-15 20:20:27 | Re: Idea for reducing planning time |