Re: Replication logging
От | Fujii Masao |
---|---|
Тема | Re: Replication logging |
Дата | |
Msg-id | AANLkTi=1VCCSUDkW1=DB814hJ8jM516zeUTGtXbvmPcZ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Replication logging (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Replication logging
|
Список | pgsql-hackers |
On Tue, Jan 18, 2011 at 4:15 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > I also find it weird that incoming replication connections are logged by > default. In the standby, we also log "streaming replication successfully > connected to primary", which serves much of the same debugging purpose. That > standby-side message is ok, we have a tradition of being more verbose during > recovery, we also emit the "restored log file \"%s\" from archive" message > for every WAL segment restored from archive for example. > > We could turn log_connections into an enum, like log_statement: > > log_connections = 'none' # none, replication, regular, all +1 We should treat log_disconnections the same? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: