Re: Default gucs for EXPLAIN

Поиск
Список
Период
Сортировка
От Guillaume Lelarge
Тема Re: Default gucs for EXPLAIN
Дата
Msg-id CAECtzeU0urPNfv4OvMviqE_ZoRKAM-YohzVW9ju5F-ZyPOqn1w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Default gucs for EXPLAIN  (David Fetter <david@fetter.org>)
Список pgsql-hackers
Le mer. 3 juin 2020 à 04:16, David Fetter <david@fetter.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.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: Transactions involving multiple postgres foreign servers, take 2
Следующее
От: Michael Paquier
Дата:
Сообщение: REINDEX CONCURRENTLY and indisreplident