From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Robert B(dot) Easter" <reaster(at)comptechnews(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | RE: WAL questions |
Date: | 2001-01-09 18:37:39 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A234D3248@sectorbase1.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Vadim is the man who ought to answer this (and he's on the
> hook to write a lot of documentation before 7.1 ships ;-)).
> But my understanding is that as of 7.1, WAL will not really
> provide any user-level features like audit trails or
> point-in-time recovery. The only useful thing it does right
> now is reduce the cost of fsyncs.
and protects against
- non-atomic disk writes (eg partially written page cleaned
up by vacuum);
- losing tuples in btree split (first step on the way to
stable indices)
> It provides an infrastructure on which we can build audit
> trails etc in future releases --- but the superstructure
> atop this infrastructure ain't there yet.
Exactly.
BTW, WAL related questions should be posted to -hackers list.
-general is not for discussion of upcoming releases.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2001-01-09 19:01:16 | Re: ECPG could not connect to the database. |
Previous Message | Tom Lane | 2001-01-09 18:13:59 | Re: COPY error: pqReadData() -- backend closed the channel unexpectedly |