Re: Allowing REINDEX to have an optional name

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Allowing REINDEX to have an optional name
Дата
Msg-id YsKP6wJ0+XvF+6/8@paquier.xyz
обсуждение исходный текст
Ответ на Re: Allowing REINDEX to have an optional name  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Allowing REINDEX to have an optional name  (Michael Paquier <michael@paquier.xyz>)
Re: Allowing REINDEX to have an optional name  (Simon Riggs <simon.riggs@enterprisedb.com>)
Список pgsql-hackers
Дерево обсуждения 
On Sun, Jul 03, 2022 at 05:41:31PM -0400, Tom Lane wrote:
> This is marked as Ready for Committer, but that seems unduly
> optimistic.

Please note that patch authors should not switch a patch as RfC by
themselves.  This is something that a reviewer should do.

> The cfbot shows that it's failing on all platforms ---
> and not in the same way on each, suggesting there are multiple
> problems.

A wild guess is that this comes from the patch that manipulates
get_database_name(), something that there is no need for as long as
the routine is called once in ReindexMultipleTables().
--
Michael
Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Export log_line_prefix(); useful for emit_log_hook.
Следующее
От: Yugo NAGATA
Дата:
Сообщение: Re: Prevent writes on large objects in read-only transactions