| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
| 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 01:36:50 |
| Message-ID: | 20200526013650.GD14122@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 23, 2020 at 06:16:25PM +0000, Nikolay Samokhvalov wrote:
> This is a very good improvement! Using information about buffers is my favorite
> way to optimize queries.
>
> Not having BUFFERS enabled by default means that in most cases, when asking for
> help, people send execution plans without buffers info.
>
> And it's simply in on event to type "(ANALYZE, BUFFERS)" all the time.
>
> So I strongly support this change, thank you, Vik.
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.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-05-26 01:37:33 | Re: New Feature Request |
| Previous Message | Bruce Momjian | 2020-05-26 01:21:26 | Re: New Feature Request |