pgsql: Add missing uninstallation rule for BackgroundPsql.pm

2023-05-02 Thread Peter Eisentraut
Add missing uninstallation rule for BackgroundPsql.pm Commit a4c17c8617 added in the install rule but not the uninstall rule. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7039c7cff6736780c3bbb41a90a6dfea0f581ad2 Modified Files -- src/test/perl/Makefi

pgsql: Update SQL features

2023-05-02 Thread Peter Eisentraut
Update SQL features Some updates for SQL:2023 and some new features in PostgreSQL 16. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e0bb5d0c5bcada63dc9b8a1a72a344a07bf930ce Modified Files -- src/backend/catalog/sql_feature_packages.txt | 1 - src/back

pgsql: Fix overridden callbacks in pg_rewind.

2023-05-02 Thread Daniel Gustafsson
Fix overridden callbacks in pg_rewind. The _traverse_files functions take a callback for processing files, but both the local and libpq source implementations called the function directly without using the callback argument. While there is no bug right now as the function called is the same as the

pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra

2023-05-02 Thread Tom Lane
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers. plperl, plpython, and pltcl all provide query-execution functions that are thin wrappers around SPI_execute() or its variants. The SPI functions document their row-count limit arguments clearly, as "maximum number of rows to re

pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra

2023-05-02 Thread Tom Lane
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers. plperl, plpython, and pltcl all provide query-execution functions that are thin wrappers around SPI_execute() or its variants. The SPI functions document their row-count limit arguments clearly, as "maximum number of rows to re

pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra

2023-05-02 Thread Tom Lane
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers. plperl, plpython, and pltcl all provide query-execution functions that are thin wrappers around SPI_execute() or its variants. The SPI functions document their row-count limit arguments clearly, as "maximum number of rows to re

pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra

2023-05-02 Thread Tom Lane
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers. plperl, plpython, and pltcl all provide query-execution functions that are thin wrappers around SPI_execute() or its variants. The SPI functions document their row-count limit arguments clearly, as "maximum number of rows to re

pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra

2023-05-02 Thread Tom Lane
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers. plperl, plpython, and pltcl all provide query-execution functions that are thin wrappers around SPI_execute() or its variants. The SPI functions document their row-count limit arguments clearly, as "maximum number of rows to re

pgsql: Doc: clarify behavior of row-limit arguments in the PLs' SPI wra

2023-05-02 Thread Tom Lane
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers. plperl, plpython, and pltcl all provide query-execution functions that are thin wrappers around SPI_execute() or its variants. The SPI functions document their row-count limit arguments clearly, as "maximum number of rows to re

pgsql: Fix assertion failure in apply worker.

2023-05-02 Thread Amit Kapila
Fix assertion failure in apply worker. During exit, the logical replication apply worker tries to release session level locks, if any. However, if the apply worker exits due to an error before its connection is initialized, trying to release locks can lead to assertion failure. The locks will be a