Index functions and INDEX_CREATE_SKIP_BUILD

From: Antonin Houska <ah(at)cybertec(dot)at>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Index functions and INDEX_CREATE_SKIP_BUILD
Date: 2025-12-02 07:18:48
Message-ID: 5275.1764659928@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2025-12-02 07:19:13 RE: Parallel Apply
Previous Message Michael Paquier 2025-12-02 07:09:58 Re: Refactor how we form HeapTuples for CatalogTuple(Insert|Update)