| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication logging |
| Date: | 2011-01-18 19:32:35 |
| Message-ID: | 4D35EAD3.3000800@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
All,
Just speaking as someone who does a lot of log-crunching for performance
review, I don't find having a separate log_connections option for
replication terribly useful. It's easy enough for me to just log all
connections and filter for the type of connections I want.
Even in cases where there's a ton of connection activity (e.g. PHP
webapp without a connection pool) logging all connections still doesn't
generate that many MB of output, in my experience.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-18 19:42:25 | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |
| Previous Message | Robert Haas | 2011-01-18 19:16:02 | Re: limiting hint bit I/O |