Re: Index functions and INDEX_CREATE_SKIP_BUILD

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Index functions and INDEX_CREATE_SKIP_BUILD
Date: 2025-12-03 04:51:44
Message-ID: aS_B4LBxfgP3CZeX@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 02, 2025 at 09:07:54AM +0100, Antonin Houska wrote:
> I'm just wondering if these measures regarding GUCs and security context are
> necessary at this place. I think that no index functions should be called if
> we only create the catalog entry for the index, but I may be mistaken.

See commit a117cebd638d, particularly the test case in privileges.sql
that this commit has added with a REINDEX CONCURRENTLY at the bottom.
You should see a function execution with an assertion failure if you
attempt to remove the stack you are mentioning..
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-12-03 05:00:31 Re: Extended Statistics set/restore/clear functions.
Previous Message Tom Lane 2025-12-03 04:43:48 Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY