Re: confusing message about archive failures
От | Daniel Farina |
---|---|
Тема | Re: confusing message about archive failures |
Дата | |
Msg-id | CAAZKuFZ9Pz7LZVs=7rz9-LySUSSRaZGGyQ58kA_Z++LqvmUD9g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: confusing message about archive failures (Jeff Janes <jeff.janes@gmail.com>) |
Список | pgsql-hackers |
On Wed, Apr 17, 2013 at 7:33 PM, Jeff Janes <jeff.janes@gmail.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.
В списке pgsql-hackers по дате отправления: