Re: TAP tests vs log_error verbosity=verbose

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: TAP tests vs log_error verbosity=verbose
Дата
Msg-id 1153281.1659284096@sss.pgh.pa.us
обсуждение исходный текст
Ответ на TAP tests vs log_error verbosity=verbose  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: TAP tests vs log_error verbosity=verbose  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Twice recently (b998196bb5 and 19408aae7f) I have had to adjust new TAP
> tests to handle log_error_verbosity=verbose, and there's a third case
> needing adjustment in the new auto_explain tests (7c34555f8c). I'm
> wondering if it would be better to set log_error_verbosity to default
> for TAP tests, no matter what's in TEMP_CONFIG.  An individual TAP test
> could still set log_error_verbosity=verbose explicitly if it wanted it.

> If not I'm going to change one of my buildfarm animals to use
> log_error_verbosity=verbose so we catch things like this earlier.

I think it's good to be able to enable log_error_verbosity=verbose
in case you need to track down some kind of problem.  So I'd vote
for your second approach.

7c34555f8c is mine, so I'll go fix that.

            regards, tom lane



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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: TAP tests vs log_error verbosity=verbose
Следующее
От: Gianluca Calcagni
Дата:
Сообщение: Triggers should work in isolation, with a final conflict detection step