| From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
|---|---|
| To: | "Zeugswetter Andreas SB" <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: AW: AW: AW: WAL-based allocation of XIDs is insecur e |
| Date: | 2001-03-07 08:53:40 |
| Message-ID: | 04be01c0a6e4$1bc31d20$4879583f@sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Before commit or rollback the xlog is not flushed to disk, thus you can loose
> those xlog entries, but the index page might already be on disk because of
> LRU buffer reuse, no ?
No. Buffer page is written to disk *only after corresponding records are flushed
to log* (WAL means Write-Ahead-Log - write log before modifying data pages).
> Another example would be a btree reorg, like adding a level, that is partway
> through before a crash.
And this is what I hopefully fixed recently with btree runtime recovery.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2001-03-07 09:06:50 | AW: AW: AW: AW: AW: WAL-based allocation of XIDs is ins ecur e |
| Previous Message | Zeugswetter Andreas SB | 2001-03-07 08:44:24 | AW: AW: AW: AW: AW: WAL-based allocation of XIDs is ins ecur e |