Re: wal_segment size vs max_wal_size - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: wal_segment size vs max_wal_size
Date
Msg-id eeee30d0-5108-09fb-497c-ec2f9a36fee9@2ndquadrant.com
Whole thread Raw
In response to Re: wal_segment size vs max_wal_size  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: wal_segment size vs max_wal_size
List pgsql-hackers
On 9/26/16 8:38 PM, Michael Paquier wrote:
> On Mon, Sep 26, 2016 at 9:30 PM, Kuntal Ghosh
> <kuntalghosh.2007@gmail.com> wrote:
>> On Mon, Sep 26, 2016 at 5:04 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>>
>>> IIRC, there is already a patch to update the minRecoveryPoint
>>> correctly, can you check if that solves the problem for you?
>>>
>>> [1] - https://www.postgresql.org/message-id/20160609.215558.118976703.horiguchi.kyotaro%40lab.ntt.co.jp
>>>
>> +1. I've tested after applying the patch. This clearly solves the problem.
> 
> Even if many things have been discussed on this thread,
> Horiguchi-san's first patch is still the best approach found after
> several lookups and attempts when messing with the recovery code.

What is the status of that patch then?  The above thread seems to have
stopped.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: pg_dump / copy bugs with "big lines" ?
Next
From: Andrew Dunstan
Date:
Subject: Re: [GENERAL] pg_upgrade from 9.5 to 9.6 fails with "invalid argument"