pgsql: Use a bitmask for ExecInsertIndexTuples options

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use a bitmask for ExecInsertIndexTuples options
Date: 2026-02-17 17:46:26
Message-ID: E1vsP9V-001J9P-0C@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use a bitmask for ExecInsertIndexTuples options

... instead of passing a bunch of separate booleans.

Also, rearrange the argument list in a hopefully more sensible order.

Discussion: https://postgr.es/m/202602111846.xpvuccb3inbx@alvherre.pgsql
Reviewed-by: Andres Freund <andres(at)anarazel(dot)de>
Reviewed-by: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> (older version)

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b7271aa1d71acda712a372213633fdb55c1465c1

Modified Files
--------------
src/backend/commands/copyfrom.c | 14 +++++---------
src/backend/executor/execIndexing.c | 35 +++++++++++++++++-----------------
src/backend/executor/execReplication.c | 30 +++++++++++++++++++++--------
src/backend/executor/nodeModifyTable.c | 28 ++++++++++++++-------------
src/include/executor/executor.h | 15 +++++++++------
5 files changed, 68 insertions(+), 54 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2026-02-17 23:48:42 pgsql: Fix one-off issue with cache ID in objectaddress.c
Previous Message Álvaro Herrera 2026-02-17 15:44:53 pgsql: Fix memory leak in new GUC check_hook