Re: Remove source code display from \df+?

Поиск
Список
Период
Сортировка
От Isaac Morland
Тема Re: Remove source code display from \df+?
Дата
Msg-id CAMsGm5f6Cyq3sbjyb2hi1MNjadR=Q-XYr-k_06OmE0vYCF-C8g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Remove source code display from \df+?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: Remove source code display from \df+?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Sun, 22 Jan 2023 at 14:26, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2023-Jan-22, Isaac Morland wrote:

> I’ve re-written the tests to create a test-specific role and functions so
> there is no longer a dependency on the superuser name.

This one would fail the sanity check that all roles created by
regression tests need to have names that start with "regress_".

Thanks for the correction. Now I feel like I've skipped some of the readings!

Updated patch attached. Informally, I am adopting the regress_* policy for all object types.

> I pondered the notion of going with the flow and just leaving out the
> tests but that seemed like giving up too easily.

I think avoiding even more untested code is good, so +1 for keeping at
it.

Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: run pgindent on a regular basis / scripted manner
Следующее
От: Tom Lane
Дата:
Сообщение: Deadlock between logrep apply worker and tablesync worker