Horton

Re: Index functions and INDEX_CREATE_SKIP_BUILD

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Antonin Houska <ah@cybertec.at>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-12-03T04:51:44Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Make relation-enumerating operations be security-restricted operations.

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