Re: Default gucs for EXPLAIN - Mailing list pgsql-hackers

From David Fetter
Subject Re: Default gucs for EXPLAIN
Date
Msg-id 20200603021621.GT13741@fetter.org
Whole thread Raw
In response to Re: Default gucs for EXPLAIN  (Vik Fearing <vik@postgresfriends.org>)
Responses Re: Default gucs for EXPLAIN  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-hackers
On Tue, Jun 02, 2020 at 09:28:48PM +0200, Vik Fearing wrote:
> On 6/2/20 7:54 PM, David G. Johnston wrote:
> > At this point, given the original goal of the patch was to try and
> > grease a smoother path to changing the default for BUFFERS, and
> > that people seem OK with doing just that without having this
> > patch, I'd say we should just change the default and forget this
> > patch.  There hasn't been any other demand from our users for this
> > capability and I also doubt that having BUFFERS on by default is
> > going to bother people.
> 
> What about WAL?  Can we turn that one one by default, too?
> 
> I often find having VERBOSE on helps when people don't qualify their
> columns and I don't know the schema.  We should turn that on by
> default, as well.

+1 for all on (except ANALYZE because it would be a foot cannon) by
default. For those few to whom it really matters, there'd be OFF
switches.

Best,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Removal of currtid()/currtid2() and some table AM cleanup
Next
From: Tom Lane
Date:
Subject: Re: Removal of currtid()/currtid2() and some table AM cleanup