From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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-06-01 01:00:25 |
Message-ID: | 20200601010025.GS13741@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 26, 2020 at 02:49:46AM +0000, Nikolay Samokhvalov wrote:
> On Mon, May 25, 2020 at 6:36 PM, Bruce Momjian < bruce(at)momjian(dot)us > 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 for changing the default of BUFFERS to ON.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-06-01 01:57:29 | Re: segmentation fault using currtid and partitioned tables |
Previous Message | Vik Fearing | 2020-05-31 23:30:21 | Re: Compatible defaults for LEAD/LAG |