AW: AW: AW: AW: AW: WAL-based allocation of XIDs is ins ecur e

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Vadim Mikheev'" <vmikheev(at)sectorbase(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: AW: AW: AW: AW: WAL-based allocation of XIDs is ins ecur e
Date: 2001-03-07 09:06:50
Message-ID: 11C1E6749A55D411A9670001FA68796336822D@sdexcsrv1.f000.d0188.sd.spardat.at
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).

You mean, that for each dirty buffer that is reused, the reusing backend fsyncs
the xlog before writing the buffer to disk ?

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim Mikheev 2001-03-07 09:07:53 Re: Proposed WAL changes
Previous Message Vadim Mikheev 2001-03-07 08:53:40 Re: AW: AW: AW: AW: WAL-based allocation of XIDs is insecur e