Re: Postgres 8.3 archive_command
От | Zeugswetter Andreas ADI SD |
---|---|
Тема | Re: Postgres 8.3 archive_command |
Дата | |
Msg-id | E1539E0ED7043848906A8FF995BDA579029136FE@m0143.s-mxs.net обсуждение исходный текст |
Ответ на | Re: Postgres 8.3 archive_command (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: Postgres 8.3 archive_command
|
Список | pgsql-hackers |
> 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. Wouldn't it be more useful to increase the WAL segment size on such installations that switch WAL files so frequently that it is a problem for the log ? This currently needs a recompile. I wondered for some time now whether 16 Mb isn't too low for current hw. Maybe it is time for making WAL segment size changeable in the conf with a clean shutdown. Andreas
В списке pgsql-hackers по дате отправления: