Re: WAL replay bugs - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: WAL replay bugs
Date
Msg-id 20141105124600.GG1791@alvin.alvh.no-ip.org
Whole thread Raw
In response to Re: WAL replay bugs  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier wrote:

> Now, do we really want this feature in-core? That's somewhat a duplicate of
> what is mentioned here:
> http://www.postgresql.org/message-id/CAB7nPqQMq=4eJAK317mxZ4Has0i+1rSLBQU29zx18JwLB2j1OA@mail.gmail.com
> Of course both things do not have the same coverage as the former is for
> buildfarm and dev, while the latter is dedidated to production systems, but
> could be used for development as well.

Oh, I had forgotten that other patch.

> The patch sent there is a bit outdated, but a potential implementation gets
> simpler with XLogReadBufferForRedo able to return flags about each block
> state during redo. I am still planning to come back to it for this cycle,
> though I stopped for now waiting for the WAL format patches finish to shape
> the APIs this feature would rely on.

I agree it makes sense to wait until the WAL reworks are done -- glad
to hear you're putting some time in this area.

Thanks,

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Sequence Access Method WIP
Next
From: Atri Sharma
Date:
Subject: Representing a SRF return column in catalogs