pgsql: libpq: Add sslcertmode option to control client certificates

libpq: Add sslcertmode option to control client certificates The sslcertmode option controls whether the server is allowed and/or required to request a certificate from the client. There are three modes: - "allow" is the default and follows the current behavior, where a configured client

pgsql: meson: add install-{docs,doc-html,doc-man} targets

meson: add install-{docs,doc-html,doc-man} targets Discussion: https://postgr.es/m/3fc3bb9b-f7f8-d442-35c1-ec82280c5...@enterprisedb.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f13eb16485fec7958a59f263827b2333dea93e59 Modified Files --

pgsql: meson: add install-{quiet, world} targets

meson: add install-{quiet, world} targets To define our own install target, we need dependencies on the i18n targets, which we did not collect so far. Discussion: https://postgr.es/m/3fc3bb9b-f7f8-d442-35c1-ec82280c5...@enterprisedb.com Branch -- master Details ---

pgsql: meson: make install_test_files more generic, rename to install_f

meson: make install_test_files more generic, rename to install_files Now it supports installing directories and directory contents as well. This will be used in a subsequent patch to install documentation. Discussion: https://postgr.es/m/3fc3bb9b-f7f8-d442-35c1-ec82280c5...@enterprisedb.com

pgsql: Doc: Improve description of the "batch_size" option for postgres

Doc: Improve description of the "batch_size" option for postgres_fdw. Document that the actual number of rows postgres_fdw inserts at once in the COPY case is determined in a similar way to the INSERT case, but it has a restriction that does not apply to the INSERT case. Follow-up for commit

pgsql: Rewrite error message related to sslmode in libpq

Rewrite error message related to sslmode in libpq The same error message will be used for a different option, to be introduced in a separate patch. Reshaping the error message as done here saves in translation. Extracted from a larger patch by the same author. Author: Jacob Champion

pgsql: Rename fields in pgstat structures for functions and relations

Rename fields in pgstat structures for functions and relations This commit renames the members of a few pgstat structures related to functions and relations, by respectively removing their prefix "f_" and "t_". The statistics for functions and relations and handled in their own file, and

pgsql: Implement find_my_exec()'s path normalization using realpath(3).

Implement find_my_exec()'s path normalization using realpath(3). Replace the symlink-chasing logic in find_my_exec with realpath(3), which has been required by POSIX since SUSv2. (Windows lacks realpath(), but there we can use _fullpath() which is functionally equivalent.) The main benefit of

pgsql: doc: fix another case of missing productname markup

doc: fix another case of missing productname markup As a follow-up commit to 0f85db92b9, this adds markup to another case of "PostgreSQL". Author: Hayato Kuroda Discussion: https://postgr.es/m/tyapr01mb58667a7c8317e267467cc599f5...@tyapr01mb5866.jpnprd01.prod.outlook.com Branch -- master

pgsql: Count updates that move row to a new page.

Count updates that move row to a new page. Add pgstat counter to track row updates that result in the successor version going to a new heap page, leaving behind an original version whose t_ctid points to the new version. The current count is shown by the n_tup_newpage_upd column of each of the

Re: pgsql: Handle the "und" locale in ICU versions 54 and older.

Jeff Davis writes: > Handle the "und" locale in ICU versions 54 and older. > The "und" locale is an alternative spelling of the root locale, but it > was not recognized until ICU 55. To maintain common behavior across > all supported ICU versions, check for "und" and replace with "root" > before

pgsql: Handle the "und" locale in ICU versions 54 and older.

Handle the "und" locale in ICU versions 54 and older. The "und" locale is an alternative spelling of the root locale, but it was not recognized until ICU 55. To maintain common behavior across all supported ICU versions, check for "und" and replace with "root" before opening. Previously, the

pgsql: amcheck: Fix a few bugs in new update chain validation.

amcheck: Fix a few bugs in new update chain validation. We shouldn't set successor[whatever] to an offset number that is less than FirstOffsetNumber or more than maxoff. We already avoided that for redirects, but not for CTID links. Allowing bad offset numbers into the successor[] array causes

pgsql: Add missing "-I." flag when building pg_bsd_indent.

Add missing "-I." flag when building pg_bsd_indent. This is evidently not required by most compilers, but buildfarm member fairywren is unhappy without it. It looks like the meson infrastructure has this right already. Branch -- master Details ---

pgsql: Unify buffer sizes in pg_dump compression API

Unify buffer sizes in pg_dump compression API Prior to the introduction of the compression API in e9960732a9, pg_dump would use the ZLIB_IN_SIZE/ZLIB_OUT_SIZE to size input/output buffers. Commit 0da243fed0 introduced similar constants for LZ4, but while gzip defined both buffers to be 4kB, LZ4

pgsql: Minor comment improvements for compress_lz4

Minor comment improvements for compress_lz4 Author: Tomas Vondra Reviewed-by: Georgios Kokolatos, Justin Pryzby Discussion: https://postgr.es/m/33496f7c-3449-1426-d568-63f6bca2a...@gmail.com Branch -- master Details ---

pgsql: Improve type handling in pg_dump's compress file API

Improve type handling in pg_dump's compress file API After 0da243fed0 got committed, we've received a report about a compiler warning, related to the new LZ4File_gets() function: compress_lz4.c: In function 'LZ4File_gets': compress_lz4.c:492:19: warning: comparison of unsigned expression in

pgsql: Wrap ICU ucol_open().

Wrap ICU ucol_open(). Hide details of supporting older ICU versions in a wrapper function. The current code only needs to handle icu_set_collation_attributes(), but a subsequent commit will add additional version-specific code. Discussion:

pgsql: Ignore generated columns during apply of update/delete.

Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber

pgsql: Ignore generated columns during apply of update/delete.

Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber

pgsql: Ignore generated columns during apply of update/delete.

Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber

pgsql: Ignore generated columns during apply of update/delete.

Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber

pgsql: Ignore generated columns during apply of update/delete.

Ignore generated columns during apply of update/delete. We fail to apply updates and deletes when the REPLICA IDENTITY FULL is used for the table having generated columns. We didn't use to ignore generated columns while doing tuple comparison among the tuples from the publisher and subscriber