| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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-02 19:28:48 |
| Message-ID: | ca746d8a-7121-78b8-c105-76d53726581b@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2020-06-02 19:29:09 | Re: Default gucs for EXPLAIN |
| Previous Message | Andrew Dunstan | 2020-06-02 18:45:11 | Re: OpenSSL 3.0.0 compatibility |