Re: Default gucs for EXPLAIN

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Vik Fearing <vik(at)postgresfriends(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Default gucs for EXPLAIN
Date: 2020-05-26 03:17:22
Message-ID: d8009d12c2b7e6fcfb42473b49eb247c60c2746a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2020-05-26 at 02:49 +0000, Nikolay Samokhvalov wrote:
> > I am not excited about this new feature. Why do it only for EXPLAIN? That is a log of GUCs. I can see this becoming a feature creep disaster.
> >
>
> How about changing the default behavior, making BUFFERS enabled by default? Those who don't need it, always can say BUFFERS OFF — the say as for TIMING.

+1

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2020-05-26 03:17:46 Re: what can go in root.crt ?
Previous Message Michael Paquier 2020-05-26 03:00:57 Re: segmentation fault using currtid and partitioned tables