Index functions and INDEX_CREATE_SKIP_BUILD
Antonin Houska <ah@cybertec.at>
From: Antonin Houska <ah@cybertec.at>
To: pgsql-hackers@lists.postgresql.org
Date: 2025-12-02T07:18:48Z
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 →
-
Make relation-enumerating operations be security-restricted operations.
- a117cebd638d 15.0 cited
In ReindexRelationConcurrently(), the call of index_concurrently_create_copy() is enclosed in /* * Switch to the table owner's userid, so that any index functions are * run as that user. Also lock down security-restricted operations * and arrange to make GUC variable changes local to this command. */ GetUserIdAndSecContext(&save_userid, &save_sec_context); SetUserIdAndSecContext(heapRel->rd_rel->relowner, save_sec_context | SECURITY_RESTRICTED_OPERATION); save_nestlevel = NewGUCNestLevel(); and /* Roll back any GUC changes executed by index functions */ AtEOXact_GUC(false, save_nestlevel); /* Restore userid and security context */ SetUserIdAndSecContext(save_userid, save_sec_context); Which index functions can be called if index_create() receives the INDEX_CREATE_SKIP_BUILD flag? -- Antonin Houska Web: https://www.cybertec-postgresql.com