Re: Replication logging

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Replication logging
Date: 2011-01-17 06:53:15
Message-ID: AANLkTimwwsUQSTOSh5WwjS7KSL1JqFoT9auGyYb7Vh56@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 17, 2011 at 03:06, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Jan 16, 2011 at 9:19 AM, Magnus Hagander <magnus(at)hagander(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2011-01-17 07:13:28 Re: texteq/byteaeq: avoid detoast [REVIEW]
Previous Message Magnus Hagander 2011-01-17 06:52:28 Re: Streaming base backups