| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication logging |
| Date: | 2011-01-19 17:05:39 |
| Message-ID: | 21392.1295456739@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Simon Riggs wrote:
>> I'm particularly concerned that people make such changes too quickly.
>> There are many things in this area of code that need changing, but also
>> many more that do not. If we are to move forwards we need to avoid going
>> one step forwards, one step back.
> There were enough people who wanted a change that we went ahead and did
> it --- if there was lack of agreement, we would have delayed longer.
The real reason why we changed this is that nobody (except Simon) sees
a situation where unconditional logging of successful replication
connections is especially helpful. If you were trying to diagnose a
problem you would more likely need to know about *failed* connections,
but the code that was in there didn't provide that. At least not unless
you turned on log_connections ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-01-19 17:10:16 | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |
| Previous Message | Pavel Stehule | 2011-01-19 17:01:09 | Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |