| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jd(at)commandprompt(dot)com, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org, Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Subject: | Re: syslog_line_prefix |
| Date: | 2009-09-25 20:33:59 |
| Message-ID: | 9837222c0909251333m1ad26958ra487c82690e48446@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 25, 2009 at 22:18, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Sep 25, 2009 at 4:06 PM, Magnus Hagander <magnus(at)hagander(dot)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...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-25 20:36:39 | formrdesc() versus relation rowtype OIDs |
| Previous Message | Magnus Hagander | 2009-09-25 20:32:31 | Re: syslog_line_prefix |