Re: fix log_min_duration_statement logic error

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: fix log_min_duration_statement logic error
Date: 2003-09-27 14:06:15
Message-ID: Pine.LNX.4.44.0309271605570.11938-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane writes:

> Neil Conway <neilc(at)samurai(dot)com> writes:
> > I also don't particularly like the format of the log message (for one
> > thing, the "duration_statement" prefix in the log message shouldn't
> > include an underscore, it's not a variable or anything -- and the case
> > can be made that if we printed the duration because log_duration is set,
> > we don't need to print it again if the duration of the query exceeded
> > log_min_duration_statement), but I haven't changed it.
>
> I think there should be just one "duration: nnn" log entry, printed if
> either condition holds.

Is anyone going to take care of this?

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-09-27 14:30:45 Re: fix log_min_duration_statement logic error
Previous Message Gaetano Mendola 2003-09-27 09:27:55 Re: Waiting the patch applied