| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Log replication connections only when log_connections is on |
| Date: | 2011-01-19 14:08:31 |
| Message-ID: | AANLkTikOgTpnXp1qn-d5vNw1o5pQkiz-kxk534zhanLv@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 19, 2011 at 7:55 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> How will we diagnose erratic connection problems now?
As Heikki pointed out, the slave still logs this information, so we
can look there. If that's enough, yeah, you'll have to turn
log_connections on on the master, but I don't think that will be very
frequent, and it's not an unmanageable burden anyway.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-01-19 15:16:39 | Re: Re: [COMMITTERS] pgsql: Log replication connections only when log_connections is on |
| Previous Message | Simon Riggs | 2011-01-19 13:29:46 | Re: [COMMITTERS] pgsql: Log replication connections only when log_connections is on |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-01-19 14:13:26 | Re: limiting hint bit I/O |
| Previous Message | Joachim Wieland | 2011-01-19 14:01:46 | Re: pg_dump directory archive format / parallel pg_dump |