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

From Michael Paquier
Subject Re: wal_segment size vs max_wal_size
Date
Msg-id CAB7nPqRgvyzaQONBsfn8EBedJMQmwmdHMeR9JwTkmPCnz_ki6g@mail.gmail.com
Whole thread Raw
In response to Re: wal_segment size vs max_wal_size  (Kuntal Ghosh <kuntalghosh.2007@gmail.com>)
Responses Re: wal_segment size vs max_wal_size  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
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.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Speedup twophase transactions
Next
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql: pg_ctl: Detect current standby state from pg_control