Re: Failed archive_command copy - number of attempts configurable?

From: Daniel Harris <daniel(dot)harris(at)metaswitch(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Failed archive_command copy - number of attempts configurable?
Date: 2010-11-10 19:46:10
Message-ID: 11DE3EEC54A8A44EAD99D8C0D3FD7207A3487566DA@ENFIMBOX1.ad.datcon.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Fujii, thank you very much for this clarification.

Regards,
Dan

-----Original Message-----
From: Fujii Masao [mailto:masao(dot)fujii(at)gmail(dot)com]
Sent: 09 November 2010 11:55
To: Daniel Harris
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Failed archive_command copy - number of attempts configurable?

On Tue, Nov 9, 2010 at 4:01 AM, dan.m.harris
<daniel(dot)harris(at)metaswitch(dot)com> wrote:
> But then the primary retries this another 49 times! So 150 attempts in all.
>
> What I need to know is whether these numbers are configurable?

No.

> Can they be
> timed? How long before the primary stops retrying altogether?

Forever until the archive will have been available again.

BTW, since the primary cannot remove the unarchived WAL file from
pg_xlog directory, unless you fix the archive soon, the primary might
run out of the disk space and cause a PANIC error.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Filonenko Michael 2010-11-10 20:02:41 NOTIFY/LISTEN why is not a callback as notice processing.
Previous Message Alban Hertroys 2010-11-10 18:49:38 Re: PostgreSQL 8.2.3