Re: Adjusting debug_print_plan to be more useful by default

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Adjusting debug_print_plan to be more useful by default
Date: 2008-08-20 02:21:24
Message-ID: 18007.1219198884@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> On Tuesday 19 August 2008 12:40:11 Tom Lane wrote:
>> I'd also like to propose making debug_pretty_print default to ON.
>> At least for me, the other formatting is 100% unreadable.

> Any thoughts on just making it always print that way and getting rid of the
> GUC? Anyone want to argue they'll be turning this off?

Hmm ... I don't personally have any use for the OFF setting, but if
there's someone out there who actually wants to run with the
debug_print_xxx settings enabled for any length of time, I can see where
there'd be a log-volume problem with the pretty-printed format. Such a
person would presumably also want to do automated analysis of the
results and so wouldn't give a fig for nice whitespace anyhow.

Maybe that's a long shot, but the other side of the coin is that taking
it out isn't going to save us a thing except one GUC variable ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-08-20 02:24:13 Re: Re: [COMMITTERS] pgsql: Make the pg_stat_activity view call a SRF
Previous Message David Fetter 2008-08-20 02:19:47 Re: Adjusting debug_print_plan to be more useful by default