pgsql: Rename RowCompareType to CompareType

2025-01-14 Thread Peter Eisentraut
Rename RowCompareType to CompareType RowCompareType served as a way to describe the fundamental meaning of an operator, notionally independent of an operator class (although so far this was only really supported for btrees). Its original purpose was for use inside RowCompareExpr, and it has also

pgsql: Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c

2025-01-14 Thread Tom Lane
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c. In the name of ABI stability (that is, to avoid a library major version bump for libpq), libpq still exports a version of pqsignal() that we no longer want to use ourselves. However, since that has the same link name as the functio

pgsql: Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c

2025-01-14 Thread Tom Lane
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c. In the name of ABI stability (that is, to avoid a library major version bump for libpq), libpq still exports a version of pqsignal() that we no longer want to use ourselves. However, since that has the same link name as the functio

pgsql: Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c

2025-01-14 Thread Tom Lane
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c. In the name of ABI stability (that is, to avoid a library major version bump for libpq), libpq still exports a version of pqsignal() that we no longer want to use ourselves. However, since that has the same link name as the functio

pgsql: Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c

2025-01-14 Thread Tom Lane
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c. In the name of ABI stability (that is, to avoid a library major version bump for libpq), libpq still exports a version of pqsignal() that we no longer want to use ourselves. However, since that has the same link name as the functio

pgsql: Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c

2025-01-14 Thread Tom Lane
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c. In the name of ABI stability (that is, to avoid a library major version bump for libpq), libpq still exports a version of pqsignal() that we no longer want to use ourselves. However, since that has the same link name as the functio

pgsql: Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c

2025-01-14 Thread Tom Lane
Avoid symbol collisions between pqsignal.c and legacy-pqsignal.c. In the name of ABI stability (that is, to avoid a library major version bump for libpq), libpq still exports a version of pqsignal() that we no longer want to use ourselves. However, since that has the same link name as the functio

pgsql: Synchronize guc_tables.c categories with vacuum docs categories

2025-01-14 Thread Melanie Plageman
Synchronize guc_tables.c categories with vacuum docs categories ca9c6a5680d consolidated most of the vacuum-related GUCs' documentation into a new subsection. af2317652d5daf8b then enforced this order in postgresql.conf.sample. This commit reorganizes the GUC groups in guc_tables.c/h to match the

pgsql: Fix catcache invalidation of a list entry that's being built

2025-01-14 Thread Heikki Linnakangas
Fix catcache invalidation of a list entry that's being built If a new catalog tuple is inserted that belongs to a catcache list entry, and cache invalidation happens while the list entry is being built, the list entry might miss the newly inserted tuple. To fix, change the way we detect concurren

pgsql: psql: Add option to use expanded mode to all list commands.

2025-01-14 Thread Dean Rasheed
psql: Add option to use expanded mode to all list commands. This allows "x" to be appended to any psql list-like meta-command, forcing its output to be displayed in expanded mode. This improves readability in cases where the output is very wide. For example, "\dfx+" (or equivalently "\df+x") will

pgsql: ecpg: Restore detection of unsupported COPY FROM STDIN.

2025-01-14 Thread Fujii Masao
ecpg: Restore detection of unsupported COPY FROM STDIN. The ecpg command includes code to warn about unsupported COPY FROM STDIN statements in input files. However, since commit 3d009e45bd, this functionality has been broken due to a bug introduced in that commit, causing ecpg to fail to detect th

pgsql: ecpg: Restore detection of unsupported COPY FROM STDIN.

2025-01-14 Thread Fujii Masao
ecpg: Restore detection of unsupported COPY FROM STDIN. The ecpg command includes code to warn about unsupported COPY FROM STDIN statements in input files. However, since commit 3d009e45bd, this functionality has been broken due to a bug introduced in that commit, causing ecpg to fail to detect th

pgsql: ecpg: Restore detection of unsupported COPY FROM STDIN.

2025-01-14 Thread Fujii Masao
ecpg: Restore detection of unsupported COPY FROM STDIN. The ecpg command includes code to warn about unsupported COPY FROM STDIN statements in input files. However, since commit 3d009e45bd, this functionality has been broken due to a bug introduced in that commit, causing ecpg to fail to detect th

pgsql: ecpg: Restore detection of unsupported COPY FROM STDIN.

2025-01-14 Thread Fujii Masao
ecpg: Restore detection of unsupported COPY FROM STDIN. The ecpg command includes code to warn about unsupported COPY FROM STDIN statements in input files. However, since commit 3d009e45bd, this functionality has been broken due to a bug introduced in that commit, causing ecpg to fail to detect th

pgsql: ecpg: Restore detection of unsupported COPY FROM STDIN.

2025-01-14 Thread Fujii Masao
ecpg: Restore detection of unsupported COPY FROM STDIN. The ecpg command includes code to warn about unsupported COPY FROM STDIN statements in input files. However, since commit 3d009e45bd, this functionality has been broken due to a bug introduced in that commit, causing ecpg to fail to detect th

pgsql: ecpg: Restore detection of unsupported COPY FROM STDIN.

2025-01-14 Thread Fujii Masao
ecpg: Restore detection of unsupported COPY FROM STDIN. The ecpg command includes code to warn about unsupported COPY FROM STDIN statements in input files. However, since commit 3d009e45bd, this functionality has been broken due to a bug introduced in that commit, causing ecpg to fail to detect th

pgsql: Consistently spell "leakproof" without a hyphen.

2025-01-14 Thread Dean Rasheed
Consistently spell "leakproof" without a hyphen. The overwhelming majority of places already did this, but a small handful of places had a hyphen. Yugo Nagata. Discussion: https://postgr.es/m/CAEZATCXnnuORE2BoGwHw2zbtVvsPOLhbfVmEk9GxRzK%2Bx3OW-Q%40mail.gmail.com Branch -- master Details -

pgsql: psql: Add leakproof indicator to \df+, \do+, \dAo+, and \dC+ out

2025-01-14 Thread Dean Rasheed
psql: Add leakproof indicator to \df+, \do+, \dAo+, and \dC+ output. This allows users to determine whether particular functions are leakproof, and whether the underlying functions used by operators and casts are leakproof. This is useful to determine whether indexes can be used in queries on secu

pgsql: Fix catcache invalidation of a list entry that's being built

2025-01-14 Thread Heikki Linnakangas
Fix catcache invalidation of a list entry that's being built If a new catalog tuple is inserted that belongs to a catcache list entry, and cache invalidation happens while the list entry is being built, the list entry might miss the newly inserted tuple. To fix, change the way we detect concurren

pgsql: Fix catcache invalidation of a list entry that's being built

2025-01-14 Thread Heikki Linnakangas
Fix catcache invalidation of a list entry that's being built If a new catalog tuple is inserted that belongs to a catcache list entry, and cache invalidation happens while the list entry is being built, the list entry might miss the newly inserted tuple. To fix, change the way we detect concurren

pgsql: Fix catcache invalidation of a list entry that's being built

2025-01-14 Thread Heikki Linnakangas
Fix catcache invalidation of a list entry that's being built If a new catalog tuple is inserted that belongs to a catcache list entry, and cache invalidation happens while the list entry is being built, the list entry might miss the newly inserted tuple. To fix, change the way we detect concurren

pgsql: Fix catcache invalidation of a list entry that's being built

2025-01-14 Thread Heikki Linnakangas
Fix catcache invalidation of a list entry that's being built If a new catalog tuple is inserted that belongs to a catcache list entry, and cache invalidation happens while the list entry is being built, the list entry might miss the newly inserted tuple. To fix, change the way we detect concurren

pgsql: Fix catcache invalidation of a list entry that's being built

2025-01-14 Thread Heikki Linnakangas
Fix catcache invalidation of a list entry that's being built If a new catalog tuple is inserted that belongs to a catcache list entry, and cache invalidation happens while the list entry is being built, the list entry might miss the newly inserted tuple. To fix, change the way we detect concurren