pgsql: Use a bitmask for ExecInsertIndexTuples options - Mailing list pgsql-committers

From Álvaro Herrera
Subject pgsql: Use a bitmask for ExecInsertIndexTuples options
Date
Msg-id E1vsP9V-001J9P-0C@gemulon.postgresql.org
Whole thread Raw
List 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@anarazel.de>
Reviewed-by: Fabrízio de Royes Mello <fabriziomello@gmail.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(-)


pgsql-committers by date:

Previous
From: Álvaro Herrera
Date:
Subject: pgsql: Fix memory leak in new GUC check_hook
Next
From: Michael Paquier
Date:
Subject: pgsql: Fix one-off issue with cache ID in objectaddress.c