RE: Proposed WAL changes

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Ian Lance Taylor'" <ian(at)airs(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: Proposed WAL changes
Date: 2001-03-07 20:03:41
Message-ID: 8F4C99C66D04D4118F580090272A7A234D32F8@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > I feel that the fact that
> >
> > WAL can't help in the event of disk errors
> >
> > is often overlooked.
>
> This is true in general. But, nevertheless, WAL can be written to
> protect against predictable disk errors, when possible. Failing to
> write a couple of disk blocks when the system crashes is a reasonably
> predictable disk error. WAL should ideally be written to work
> correctly in that situation.

But what can be done if fsync returns before pages flushed?

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2001-03-07 20:48:32 Re: pg_dump writes SEQUENCEs twice with -a
Previous Message Mikheev, Vadim 2001-03-07 20:01:40 RE: Proposed WAL changes