Re: suggestion: log_statement = sample

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Janning Vygen <vygen(at)kicktipp(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: suggestion: log_statement = sample
Date: 2009-07-21 13:49:36
Message-ID: 11547.1248184176@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Janning Vygen <vygen(at)kicktipp(dot)de> writes:
> On Monday 20 July 2009 19:24:13 Bill Moran wrote:
>> Have you benchmarked the load it creates under your workload?

> Yes, it takes up to 15% of our workload in an average use case. But we have
> peak times where we can not afford 15% lost for logging!

Well, you could turn it off during the peak times. Or buy better
hardware --- if you have less than 15% headroom then it's past time
to be doing that anyway.

You really haven't given any convincing case for this behavior...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-07-21 13:55:05 Re: array_agg crash?
Previous Message Phoenix Kiula 2009-07-21 13:36:15 Re: First query very slow. Solutions: memory, or settings, or SQL?