Re: fix log_min_duration_statement logic error

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: fix log_min_duration_statement logic error
Date: 2003-10-06 01:35:53
Message-ID: 3F80C6F9.6080701@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


> The problem with two lines is that another log message could get between
> them. I agree milliseconds makes more sense for output.

That's not a huge problem. I've run our servers like that for ages, and
there's not really any time when a human can't tell what's going on.
You can also turn on PID logging as well. (Should that even be on by
default?

Chris

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2003-10-06 01:47:44 spanish translation updates
Previous Message Neil Conway 2003-10-06 00:22:38 Re: [HACKERS] Open 7.4 items