Re: Postgres 8.3 archive_command

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: Postgres 8.3 archive_command
Дата
Msg-id 474405FB.EE98.0025.0@wicourts.gov
обсуждение исходный текст
Ответ на Re: Postgres 8.3 archive_command  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-hackers
>>> On Wed, Nov 21, 2007 at  8:49 AM, in message
<1195656591.4246.42.camel@ebony.site>, Simon Riggs <simon@2ndquadrant.com>
wrote:
> Perhaps we should move the successful archived message to DEBUG1 now,
> except for the first message after the archiver starts or when the
> archive_command changes, plus one message every 255 segments? That would
> reduce the log volume in the normal case without endangering our ability
> to see what is happening.
I would prefer to always log the archives; it has proven useful in
investigating what's going on when our backup stream "stalls".  How
much other stuff would I be getting if I had to turn on DEBUG1 to
see this?  Would it be overkill to add a GUC to configure the log
level of archiving?
For less active databases, where we rarely get more than one
segment per hour, it would be kinda odd to see an archive logged
once every couple weeks.
-Kevin




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: wrong behavior using to_char() again
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Postgres 8.3 archive_command