Re: Replication logging - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Replication logging
Date
Msg-id AANLkTimwwsUQSTOSh5WwjS7KSL1JqFoT9auGyYb7Vh56@mail.gmail.com
Whole thread Raw
In response to Re: Replication logging  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Replication logging  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Mon, Jan 17, 2011 at 03:06, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sun, Jan 16, 2011 at 9:19 AM, Magnus Hagander <magnus@hagander.net> wrote:
>> Currently, replication connections *always* logs something like:
>> LOG:  replication connection authorized: user=mha host=[local]
>>
>> There's no way to turn that off.
>>
>> I can't find the reasoning behind this - why is this one not
>> controlled by log_connections like normal ones? There's a comment in
>> the code that says this is intentional, but I can't figure out why...
>
> Because it's reasonably likely that you'd want to log replication
> connections but not regular ones?  On the theory that replication is
> more important than an ordinary login?

Well, a superuser connection is even worse, but we don't hard-code
logging of those.

> What do you have in mind?

Either having it controlled by log_connections, or perhaps have a
log_highpriv_connections that controls replication *and* superuser, to
be somewhat consistent.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Streaming base backups
Next
From: Pavel Stehule
Date:
Subject: Re: texteq/byteaeq: avoid detoast [REVIEW]