pgsql: Add const qualifiers to XLogRegister*() functions

2024-09-02 Thread Peter Eisentraut
Add const qualifiers to XLogRegister*() functions Add const qualifiers to XLogRegisterData() and XLogRegisterBufData(). Several unconstify() calls can be removed. Reviewed-by: Aleksander Alekseev Discussion: https://www.postgresql.org/message-id/dd889784-9ce7-436a-b4f1-52e4a5e57...@eisentraut.o

pgsql: Fix typos and grammar in code comments and docs

2024-09-02 Thread Michael Paquier
Fix typos and grammar in code comments and docs Author: Alexander Lakhin Discussion: https://postgr.es/m/f7e514cf-2446-21f1-a5d2-8c089a6e2...@gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4236825197e8b7f26f8fd2ce0ac287a696e7264e Modified Files -

pgsql: Define PG_TBLSPC_DIR for path pg_tblspc/ in data folder

2024-09-02 Thread Michael Paquier
Define PG_TBLSPC_DIR for path pg_tblspc/ in data folder Similarly to 2065ddf5e34c, this introduces a define for "pg_tblspc". This makes the style more consistent with the existing PG_STAT_TMP_DIR, for example. There is a difference with the other cases with the introduction of PG_TBLSPC_DIR_SLASH

pgsql: Stamp 17rc1.

2024-09-02 Thread Tom Lane
Stamp 17rc1. Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/94f1474e600fdbc6b325f69903eecfeb1f69fcbd Modified Files -- configure| 18 +- configure.ac | 2 +- meson.build | 2 +- 3 files changed, 11 insertions(+), 11 deletions(

pgsql: doc: Consistently use result set in documentation

2024-09-02 Thread Daniel Gustafsson
doc: Consistently use result set in documentation We use "result set" in all other places so let's be consistent across the entire documentation. Reported-by: grantgryc...@gmail.com Discussion: https://postgr.es/m/172187924855.915373.15595156724215203...@wrigleys.postgresql.org Branch -- ma

Re: pgsql: Translation updates

2024-09-02 Thread Guillaume Lelarge
Le lun. 2 sept. 2024 à 18:49, Guillaume Lelarge a écrit : > Hi, > > Le lun. 2 sept. 2024 à 18:06, Peter Eisentraut a > écrit : > >> On 02.09.24 17:18, Tom Lane wrote: >> > Peter Eisentraut writes: >> >> Translation updates >> > >> > I'm seeing build warnings with this: >> > >> > /usr/bin/msgfmt

Re: pgsql: Translation updates

2024-09-02 Thread Guillaume Lelarge
Hi, Le lun. 2 sept. 2024 à 18:06, Peter Eisentraut a écrit : > On 02.09.24 17:18, Tom Lane wrote: > > Peter Eisentraut writes: > >> Translation updates > > > > I'm seeing build warnings with this: > > > > /usr/bin/msgfmt: po/fr.po: warning: PO file header fuzzy > > w

Re: pgsql: Translation updates

2024-09-02 Thread Peter Eisentraut
On 02.09.24 17:18, Tom Lane wrote: Peter Eisentraut writes: Translation updates I'm seeing build warnings with this: /usr/bin/msgfmt: po/fr.po: warning: PO file header fuzzy warning: older versions of msgfmt will give an error on this /usr/bin/msgfmt: po/fr.po: w

pgsql: Fix warnings from msgfmt

2024-09-02 Thread Peter Eisentraut
Fix warnings from msgfmt /usr/bin/msgfmt: po/fr.po: warning: PO file header fuzzy warning: older versions of msgfmt will give an error on this Apparently, not all versions of msgfmt produce this. Quick fix for now, more to be researched later. Branch -- REL_17_ST

Re: pgsql: Translation updates

2024-09-02 Thread Tom Lane
Peter Eisentraut writes: > On 02.09.24 17:18, Tom Lane wrote: >> I'm seeing build warnings with this: > I've fixed this manually for now. Thanks, confirmed clean build here. > I don't see these warnings with my local toolset. I'll research this > for the next release. I see it with $ rpm -q

pgsql: Fix rarely-run test for message wording change

2024-09-02 Thread Peter Eisentraut
Fix rarely-run test for message wording change fixup for 2e6a8047f0 Reported-by: Nazir Bilal Yavuz Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2befd22790ef32bbe3cbfc8b4b826e8a1286afbd Modified Files -- src/test/modules/xid_wraparound/t/002_limits.

pgsql: Fix rarely-run test for message wording change

2024-09-02 Thread Peter Eisentraut
Fix rarely-run test for message wording change fixup for 2e6a8047f0 Reported-by: Nazir Bilal Yavuz Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e6ec1d6aabe024d0789fe53c711cd5cae47d30ea Modified Files -- src/test/modules/xid_wraparound/t/002_

Re: pgsql: Translation updates

2024-09-02 Thread Tom Lane
Peter Eisentraut writes: > Translation updates I'm seeing build warnings with this: /usr/bin/msgfmt: po/fr.po: warning: PO file header fuzzy warning: older versions of msgfmt will give an error on this /usr/bin/msgfmt: po/fr.po: warning: PO file header fuzzy

pgsql: Only perform pg_strong_random init when required

2024-09-02 Thread Daniel Gustafsson
Only perform pg_strong_random init when required The random number generator in OpenSSL 1.1.1 was redesigned to provide fork safety by default, thus removing the need for calling RAND_poll after forking to ensure that two processes cannot share the same state. Since we now support 1.1.0 as the min

pgsql: Remove support for OpenSSL older than 1.1.0

2024-09-02 Thread Daniel Gustafsson
Remove support for OpenSSL older than 1.1.0 OpenSSL 1.0.2 has been EOL from the upstream OpenSSL project for some time, and is no longer the default OpenSSL version with any vendor which package PostgreSQL. By retiring support for OpenSSL 1.0.2 we can remove a lot of no longer required complexity

pgsql: Translation updates

2024-09-02 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: d0110df9f34c2d32cb2652d4477c3135dabe84f7 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/986a3ac497fddac717d40b7cd90296af27f07526 Modified Files --

pgsql: Cache typarray for fast lookups in binary upgrade mode

2024-09-02 Thread Daniel Gustafsson
Cache typarray for fast lookups in binary upgrade mode When upgrading a large schema it adds significant overhead to perform individual catalog lookups per relation in order to retrieve Oid for preserving Oid calls. This instead adds the typarray to the TypeInfo cache which then allows for fast lo

pgsql: More use of getpwuid_r() directly

2024-09-02 Thread Peter Eisentraut
More use of getpwuid_r() directly Remove src/port/user.c, call getpwuid_r() directly. This reduces some complexity and allows better control of the error behavior. For example, the old code would in some circumstances silently truncate the result string, or produce error message strings that the