From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
---|---|
To: | "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
Cc: | "'Zeugswetter Andreas SB'" <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Subject: | Re: WAL-based allocation of XIDs is insecure |
Date: | 2001-03-07 11:28:11 |
Message-ID: | 055801c0a6f9$b1ec6120$4879583f@sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> wrote:
>
> In short I do not think that the current implementation of
> "physical log" does what it was intended to do :-(
Hm, wasn't it handling non-atomic disk writes, Andreas?
And for what else "physical log" could be used?
The point was - copy entire page content on first after
checkpoint modification, so on recovery first restore page
to consistent state, so all subsequent logged modifications
could be applied without fear about page inconsistency.
Now, why should we log page as it was *before* modification?
We would log modification anyway (yet another log record!) and
would apply it to page, so result would be the same as now when
we log page after modification - consistent *modifyed* page.
?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 2001-03-07 11:45:52 | Re: WAL-based allocation of XIDs is insecure |
Previous Message | Vadim Mikheev | 2001-03-07 10:55:52 | Re: WAL-based allocation of XIDs is insecure |