Re: pgsql: Unite ReadBufferWithFork, ReadBufferWithStrategy, and - Mailing list pgsql-committers

From Heikki Linnakangas
Subject Re: pgsql: Unite ReadBufferWithFork, ReadBufferWithStrategy, and
Date
Msg-id 490C572C.2070304@enterprisedb.com
Whole thread Raw
In response to Re: pgsql: Unite ReadBufferWithFork, ReadBufferWithStrategy, and  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pgsql: Unite ReadBufferWithFork, ReadBufferWithStrategy, and  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-committers
Simon Riggs wrote:
> On Fri, 2008-10-31 at 15:05 +0000, Heikki Linnakangas wrote:
>> Log Message:
>> -----------
>> Unite ReadBufferWithFork, ReadBufferWithStrategy, and ZeroOrReadBuffer
>> functions into one ReadBufferExtended function, that takes the strategy
>> and mode as argument. There's three modes, RBM_NORMAL which is the default
>> used by plain ReadBuffer(), RBM_ZERO, which replaces ZeroOrReadBuffer, and
>> a new mode RBM_ZERO_ON_ERROR, which allows callers to read corrupt pages
>> without throwing an error. The FSM needs the new mode to recover from
>> corrupt pages, which could happend if we crash after extending an FSM file,
>> and the new page is "torn".
>
> I thought you were adding the "read buffer only if in cache" option
> also?

No, but if it's needed, it should now fit well into the infrastructure,
as a new ReadBuffer mode.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-committers by date:

Previous
From: meskes@postgresql.org (Michael Meskes)
Date:
Subject: pgsql: Use string component in index structure.
Next
From: meskes@postgresql.org (Michael Meskes)
Date:
Subject: pgsql: Move from strcmp to strncmp to be more tolerant for changes to