Re: fix log_min_duration_statement logic error - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: fix log_min_duration_statement logic error
Date
Msg-id 200310051740.h95HehT10789@candle.pha.pa.us
Whole thread Raw
In response to Re: fix log_min_duration_statement logic error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fix log_min_duration_statement logic error
Re: fix log_min_duration_statement logic error
List pgsql-patches
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > It is pretty easy to continue pulling lines after the 'duration' hit to
> > see the full query, perhap using awk, or even grep with a + arg.  I just
> > don't see why we should make it harder for folks by splitting it over
> > several lines.
>
> Somehow I fail to see how that's a consistent position.

It is easier than making things split across lines.  It is a common
request so I want to make it as easy as possible --- that seems
consistent.  If you can think of a way to make it even easier, please
let me know.

I have not heard from you why we should make it harder (split across two
lines), except for consistency with log_statement and log_duration
outputs.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: fix log_min_duration_statement logic error
Next
From: Bruce Momjian
Date:
Subject: Re: fix log_min_duration_statement logic error