Re: Allow auto_explain to log to NOTICE

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: Allow auto_explain to log to NOTICE
Дата
Msg-id EEA234AC-85E2-4173-8433-CC673AE4007A@yesql.se
обсуждение исходный текст
Ответ на Re: Allow auto_explain to log to NOTICE  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Allow auto_explain to log to NOTICE  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
(Michael: sorry for not having responded to your comments on the patch, $life
has had little time over for hacking lately)

> On 4 Jan 2019, at 13:49, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Fri, Jan 04, 2019 at 01:06:24PM +0100, Peter Eisentraut wrote:
>> Do we really want to add user-facing options just to be able to run
>> tests?  Should we write the tests differently instead?

I voiced this concern upthread as well, not being sure if it’s worth the added
complexity.

> The take is that the output of the plans generated includes data which
> is run-dependent because the duration of the plan is generated
> unconditionally.  One way to write generic tests considering this
> would be to use a TAP test, but I feel that's overdoing it just for
> this case.
>
> Being able to control if the plan duration shows up still looks like
> an interesting option to me independently of adding tests.

There is that.  We might not be excited about writing tests for this contrib
module but someone else might want to use this for testing their application in
a similar manner to how pg_regress tests?

cheers ./daniel

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] Pass COPT and PROFILE to CXXFLAGS as well
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: proposal - plpgsql unique statement id