Re: Logging checkpoints and other slowdown causes

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: "Greg Smith" <gsmith(at)gregsmith(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Logging checkpoints and other slowdown causes
Date: 2007-05-11 11:29:09
Message-ID: 1d4e0c10705110429n3e7f1f9as8eab7fcbeb610758@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On 5/11/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
> I agree that debug levels are not suitable for this.

Squid (the (reverse) proxy) has a nice feature for debugging purposes
(admin and developers). It's possible to have different logging level
for different sections of the code. For example, if you want to debug
a particular part, you can have ALL,1 33,2 in your config file which
allows you to have a more verbose debug on the section 33 of the code
(33 is ACL).
It's really useful because you can even debug a particular code path
or a misconfiguration in production without generating a huge amount
of logs.

--
Guillaume

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-05-11 11:41:36 Re: Logging checkpoints and other slowdown causes
Previous Message Zeugswetter Andreas ADI SD 2007-05-11 10:47:24 Re: Seq scans roadmap

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2007-05-11 11:41:36 Re: Logging checkpoints and other slowdown causes
Previous Message Heikki Linnakangas 2007-05-11 10:01:38 Re: Logging checkpoints and other slowdown causes