Re: Default gucs for EXPLAIN

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: David Fetter <david(at)fetter(dot)org>
Cc: Vik Fearing <vik(at)postgresfriends(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Default gucs for EXPLAIN
Date: 2020-06-03 06:51:10
Message-ID: CAECtzeU0urPNfv4OvMviqE_ZoRKAM-YohzVW9ju5F-ZyPOqn1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le mer. 3 juin 2020 à 04:16, David Fetter <david(at)fetter(dot)org> a écrit :

> 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.
>
>
+1 for all on, except ANALYZE (foot cannon as David says) and VERBOSE
(verbose is something you ask for when the usual display isn't enough).

-1 for GUCs, we already have too many of them.

--
Guillaume.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-06-03 06:53:40 REINDEX CONCURRENTLY and indisreplident
Previous Message Masahiko Sawada 2020-06-03 06:32:17 Re: Transactions involving multiple postgres foreign servers, take 2