| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CRCs |
| Date: | 2001-01-13 00:48:39 |
| Message-ID: | 24041.979346919@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> If log record was not really flushed on disk in 3. but on-disk image of
> index block was updated in 4. and system crashed after this then after
> restart recovery you'll have unlawful index tuple pointing to where?
> Who knows! No guarantee that corresponding heap tuple was flushed on
> disk.
This example doesn't seem very convincing. Wouldn't the XLOG entry
describing creation of the heap tuple appear in the log before the one
for the index tuple? Or are you assuming that both these XLOG entries
are lost due to disk drive malfeasance?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikheev, Vadim | 2001-01-13 00:55:08 | RE: CRCs |
| Previous Message | The Hermit Hacker | 2001-01-13 00:43:14 | Re: CVS updates on committers list... |