From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Phil Endecott <spam_from_pgsql_lists(at)chezphil(dot)org> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Replication failure, slave requesting old segments |
Date: | 2018-08-13 00:19:16 |
Message-ID: | 2b671d4c-1504-9a38-3ad0-5dafe8fab92c@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/12/2018 03:54 PM, Stephen Frost wrote:
> Greetings,
>
> * Phil Endecott (spam_from_pgsql_lists(at)chezphil(dot)org) wrote:
>> OK. I think this is perhaps a documentation bug, maybe a missing
>> warning when the master reads its configuration, and maybe (as you say)
>> a bad default value.
>
> If we consider it to be an issue worthy of a change then we should
> probably just change the default value, and maybe not even allow it to
> be set lower than '1'.
>
I would say leave the default at 0 as it leaves no doubt that you are
performing without a net. A setting of '1' implies you are covered and
for a fast moving cluster or slow moving one with sufficient downtime
that would not be the case. Better to let the end user know this is not
a simple problem and some thought needs to go into configuration.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Williams | 2018-08-13 00:41:34 | Safe operations? |
Previous Message | Adrian Klaver | 2018-08-13 00:14:32 | Re: Replication failure, slave requesting old segments |