Re: confusing message about archive failures

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: confusing message about archive failures
Date: 2013-04-19 20:57:24
Message-ID: CAAZKuFZ9Pz7LZVs=7rz9-LySUSSRaZGGyQ58kA_Z++LqvmUD9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 17, 2013 at 7:33 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Wednesday, April 17, 2013, Peter Eisentraut wrote:
>>
>> When archive_command fails three times, it prints this message into the
>> logs:
>>
>> "transaction log file \"%s\" could not be archived: too many failures"
>>
>> This leaves it open what happens next. What will actually happen is
>> that it will usually try again after 60 seconds or so, but the message
>> indicates something much more fatal than that.
>>
>> Could we rephrase this a little bit to make it less dramatic, like
>>
>> "... too many failures, will try again later"
>>
>> ?
>
>
> +1 I've found the current message alarming/confusing as well. But I don't
> really understand the logic behind bursting the attempts, 3 of them one
> second apart, then sleeping 57 seconds, in the first place.

Same. By now I am numb, but when I was first rolling out archives
ages ago the message was cause for more much alarm than was indicated.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2013-04-19 21:19:46 Re: Multi-pass planner
Previous Message Tom Lane 2013-04-19 17:38:12 Re: elog() error, trying CURENT OF with foreign table