Re: syslog_line_prefix - Mailing list pgsql-hackers

From Robert Haas
Subject Re: syslog_line_prefix
Date
Msg-id 603c8f070909251402v674a00c2wc3ec85216f1306ef@mail.gmail.com
Whole thread Raw
In response to Re: syslog_line_prefix  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Fri, Sep 25, 2009 at 4:33 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Fri, Sep 25, 2009 at 22:18, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Fri, Sep 25, 2009 at 4:06 PM, Magnus Hagander <magnus@hagander.net> wrote:
>>> Other than if you're logging all your queries (or over <n> time, where
>>> <n> is very small), I've never seen a system with performance issues
>>> from logging. I'm sure others may have, but not me.
>>>
>>> Is there really any log output other than the
>>> query-logging-for-performance-analysis that is likely to cause any
>>> real load on the system? If not, perhaps we need to break out that
>>> part to a separate codepath instead, and optimize that one for speed,
>>> while optimizing the other paths for flexibility?
>>
>> Not sure, but I doubt it's that easy.
>
> If we are talking about the "log query duration" or "log queries
> longer than <n>" that's a single location in the code. It can't be
> that hard...

I'm not sure that's really the only thing that can cause a logging
bottleneck.  I would be kinda surprised.

...Robert


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot Standby 0.2.1
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Unicode escapes in E'...' strings Author: Marko Kreen