pgsql: Improve notation of BuiltinTrancheNames

2024-01-24 Thread Alvaro Herrera
Improve notation of BuiltinTrancheNames Use C99 designated initializer syntax for array elements, instead of writing the position in a comment. This is less verbose and much more readable. Akin to cc150596341e. One disadvantage is that the BuiltinTrancheNames array now has a hole of 51 NULLs --

pgsql: Add temporal PRIMARY KEY and UNIQUE constraints

2024-01-24 Thread Peter Eisentraut
Add temporal PRIMARY KEY and UNIQUE constraints Add WITHOUT OVERLAPS clause to PRIMARY KEY and UNIQUE constraints. These are backed by GiST indexes instead of B-tree indexes, since they are essentially exclusion constraints with = for the scalar parts of the key and && for the temporal part. Auth

pgsql: Rename index "abc" in aggregates.sql

2024-01-24 Thread Alexander Korotkov
Rename index "abc" in aggregates.sql In order to prevent name collision with table "abc" in namespace.sql. Reported-by: Nathan Bossart Discussion: https://postgr.es/m/20240124173735.GA2708416%40nathanxps13 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b91f9187082

pgsql: Track LLVM 18 changes.

2024-01-24 Thread Thomas Munro
Track LLVM 18 changes. A function was given a newly standard name from C++20 in LLVM 16. Then LLVM 18 added a deprecation warning for the old name, and it is about to ship, so it's time to adjust that. Back-patch to all supported releases. Discussion: https://www.postgresql.org/message-id/CA+h

pgsql: Track LLVM 18 changes.

2024-01-24 Thread Thomas Munro
Track LLVM 18 changes. A function was given a newly standard name from C++20 in LLVM 16. Then LLVM 18 added a deprecation warning for the old name, and it is about to ship, so it's time to adjust that. Back-patch to all supported releases. Discussion: https://www.postgresql.org/message-id/CA+h

pgsql: Track LLVM 18 changes.

2024-01-24 Thread Thomas Munro
Track LLVM 18 changes. A function was given a newly standard name from C++20 in LLVM 16. Then LLVM 18 added a deprecation warning for the old name, and it is about to ship, so it's time to adjust that. Back-patch to all supported releases. Discussion: https://www.postgresql.org/message-id/CA+h

pgsql: Track LLVM 18 changes.

2024-01-24 Thread Thomas Munro
Track LLVM 18 changes. A function was given a newly standard name from C++20 in LLVM 16. Then LLVM 18 added a deprecation warning for the old name, and it is about to ship, so it's time to adjust that. Back-patch to all supported releases. Discussion: https://www.postgresql.org/message-id/CA+h

pgsql: Track LLVM 18 changes.

2024-01-24 Thread Thomas Munro
Track LLVM 18 changes. A function was given a newly standard name from C++20 in LLVM 16. Then LLVM 18 added a deprecation warning for the old name, and it is about to ship, so it's time to adjust that. Back-patch to all supported releases. Discussion: https://www.postgresql.org/message-id/CA+h

pgsql: Track LLVM 18 changes.

2024-01-24 Thread Thomas Munro
Track LLVM 18 changes. A function was given a newly standard name from C++20 in LLVM 16. Then LLVM 18 added a deprecation warning for the old name, and it is about to ship, so it's time to adjust that. Back-patch to all supported releases. Discussion: https://www.postgresql.org/message-id/CA+h

pgsql: Add progress reporting of skipped tuples during COPY FROM.

2024-01-24 Thread Masahiko Sawada
Add progress reporting of skipped tuples during COPY FROM. 9e2d870119 enabled the COPY command to skip malformed data, however there was no visibility into how many tuples were actually skipped during the COPY FROM. This commit adds a new "tuples_skipped" column to pg_stat_progress_copy view to r

pgsql: jit: Require at least LLVM 10.

2024-01-24 Thread Thomas Munro
jit: Require at least LLVM 10. Remove support for older LLVM versions. The default on common software distributions will be at least LLVM 10 when PostgreSQL 17 ships. Reviewed-by: Peter Eisentraut Discussion: https://postgr.es/m/CA%2BhUKGLhNs5geZaVNj2EJ79Dx9W8fyWUU3HxcpZy55sMGcY%3DiA%40mail.gm

pgsql: Fix comment on gist_stratnum_btree

2024-01-24 Thread Peter Eisentraut
Fix comment on gist_stratnum_btree We give results for <, <=, =, >=, and >, not just =. Because why not? Author: Paul A. Jungwirth Discussion: https://www.postgresql.org/message-id/flat/CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mdhcy4_qq0+noc...@mail.gmail.com Branch -- master Details --- htt

pgsql: Allow to enable failover property for replication slots via SQL

2024-01-24 Thread Amit Kapila
Allow to enable failover property for replication slots via SQL API. This commit adds the failover property to the replication slot. The failover property indicates whether the slot will be synced to the standby servers, enabling the resumption of corresponding logical replication after failover.