Re: where did debug_print_query go in 7.3??? - Mailing list pgsql-general

From Bruce Momjian
Subject Re: where did debug_print_query go in 7.3???
Date
Msg-id 200212042143.gB4LhAN09306@candle.pha.pa.us
Whole thread Raw
In response to Re: where did debug_print_query go in 7.3???  (Joseph Shraibman <jks@selectacast.net>)
Responses Re: where did debug_print_query go in 7.3???  (Joseph Shraibman <jks@selectacast.net>)
List pgsql-general
Joseph Shraibman wrote:
> Joseph Shraibman wrote:
> > How come debug_print_query isn't in 7.3??? I need that to develop my
> > application.
> >
> Nevermind, found it. It was renamed to log_statement. May I suggest that the default
> config file have more comments in it?

Release notes have info about those changes.  More log_* changes coming
for 7.4, again will be in the release notes.

> > Also the docs haven't been fully updated. runtime-config.html has:
> >
> > DEBUG_PRINT_PARSE (boolean)
> > DEBUG_PRINT_REWRITTEN (boolean)
> > DEBUG_PRINT_PLAN (boolean)
> > DEBUG_PRETTY_PRINT (boolean)
> >
> >     These flags enable various debugging output to be sent to the server
> > log. For each executed query, print either the query text, the resulting
> >                                ^^^^^^^^^^^^
> Still needs to be fixed.

Updated.  Thanks.

--
  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-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Query breaking with unknown expression type (lost subquery from v iew?)
Next
From: wsheldah@lexmark.com
Date:
Subject: Re: Postgresql -- initial impressions and comments