| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication logging |
| Date: | 2011-01-18 16:33:16 |
| Message-ID: | AANLkTinggUcdFRhSZHXbocvaOKB3NU2X3VqL3gcQ2hMy@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 18, 2011 at 2:15 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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.
Oh, good point. All right, I withdraw my objection. Let's just make
it all controlled by log_connections and go home.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-18 16:44:16 | Re: texteq/byteaeq: avoid detoast [REVIEW] |
| Previous Message | Robert Haas | 2011-01-18 16:32:10 | Re: texteq/byteaeq: avoid detoast [REVIEW] |