Re: Allowing REINDEX to have an optional name - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Allowing REINDEX to have an optional name
Date
Msg-id YsKP6wJ0+XvF+6/8@paquier.xyz
Whole thread Raw
In response to Re: Allowing REINDEX to have an optional name  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing REINDEX to have an optional name
Re: Allowing REINDEX to have an optional name
List 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

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Export log_line_prefix(); useful for emit_log_hook.
Next
From: Yugo NAGATA
Date:
Subject: Re: Prevent writes on large objects in read-only transactions