Re: wal_segment size vs max_wal_size

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: wal_segment size vs max_wal_size
Date: 2016-09-27 00:38:08
Message-ID: CAB7nPqRgvyzaQONBsfn8EBedJMQmwmdHMeR9JwTkmPCnz_ki6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 26, 2016 at 9:30 PM, Kuntal Ghosh
<kuntalghosh(dot)2007(at)gmail(dot)com> wrote:
> On Mon, Sep 26, 2016 at 5:04 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-09-27 00:45:41 Re: [COMMITTERS] pgsql: pg_ctl: Detect current standby state from pg_control
Previous Message Michael Paquier 2016-09-27 00:30:02 Re: Speedup twophase transactions