Re: During promotion, new master tries to archive same segment twice

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Phil Endecott <spam_from_pgsql_lists(at)chezphil(dot)org>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: During promotion, new master tries to archive same segment twice
Date: 2018-08-16 13:57:18
Message-ID: b0979e77-fe08-091d-cdd8-43eaece422d2@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 08/16/2018 01:48 AM, Phil Endecott wrote:
> Adrian Klaver wrote:
>> On 08/15/2018 01:25 PM, Phil Endecott wrote:
>>> Dear Experts,
>>>

>> The above is not clear to me. My best guess:
>>

> It's not part of the error for the archive command; it's just the
> next thing in the log file.  Y is (1) trying write WAL segment
> E8 to the Y-to-Z archive and failing because it is already there and
> (2) trying to read WAL segment E9 from the X-to-Y archive and failing
> because it doesn't exist (and never will).  (1) is the problem, (2) is
> expected.

Hmm, still not sure why they are both showing up in the same LOG: entry
as the entry was for the failure of the archive_command.

What is archive_mode set to on Y?

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2018-08-16 13:57:39 Re: regex match and special characters
Previous Message Vikas Sharma 2018-08-16 13:41:31 Copy over large data Postgresql 9.5