pgsql: Remove configure check for z_streamp

2023-08-07 Thread Peter Eisentraut
Remove configure check for z_streamp This is surely obsolete. zlib version 1.0.4, which includes z_streamp, was released 1996-07-24. When this check was put in in 2001 (19c97b8579), the commit was already labeling that release as ancient. Reviewed-by: Tristan Partin Discussion: https://www.po

pgsql: Improve const use in zlib-using code

2023-08-07 Thread Peter Eisentraut
Improve const use in zlib-using code If we define ZLIB_CONST before including zlib.h, zlib augments some interfaces with const decorations. By doing that we can keep our own interfaces cleaner and can remove some unconstify calls. ZLIB_CONST was introduced in zlib 1.2.5.2 (17 Dec 2011). When co

pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread David Rowley
Don't Memoize lateral joins with volatile join conditions The use of Memoize was already disabled in normal joins when the join conditions had volatile functions per the code in match_opclause_to_indexcol(). Ordinarily, the parameterization for the inner side of a nested loop will be an Index Sca

pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread David Rowley
Don't Memoize lateral joins with volatile join conditions The use of Memoize was already disabled in normal joins when the join conditions had volatile functions per the code in match_opclause_to_indexcol(). Ordinarily, the parameterization for the inner side of a nested loop will be an Index Sca

pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread David Rowley
Don't Memoize lateral joins with volatile join conditions The use of Memoize was already disabled in normal joins when the join conditions had volatile functions per the code in match_opclause_to_indexcol(). Ordinarily, the parameterization for the inner side of a nested loop will be an Index Sca

pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread David Rowley
Don't Memoize lateral joins with volatile join conditions The use of Memoize was already disabled in normal joins when the join conditions had volatile functions per the code in match_opclause_to_indexcol(). Ordinarily, the parameterization for the inner side of a nested loop will be an Index Sca

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 1168da8e78b0511c8bfa99ceb08e848fbaa7e8f2 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0fee069960a65a22e92923d5406fcb9dae5d794c Modified Files --

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 97398d714ace69f0c919984e160f429b6fd2300e Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2bdd7b262f7af28dec11684bd8998f7dc2acc793 Modified Files -

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 2cfadec9afd05853f9bf6dd83f6cf7fe96f9f3cf Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/2f89d0c97d25fdb7920a5709267f996ef47fcebd Modified Files --

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 97398d714ace69f0c919984e160f429b6fd2300e Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e8386b2cef7741aa4e49870691d67f792d5f6789 Modified Files --

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 2ac4b26db0a9032bce0eb018f6f742cea5847118 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6186e2775e0c159e9e4fc4d8df23f8d5e66dccce Modified Files --

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: f6a99caeb18f1106ee1c619801b6eb5f3fef10a4 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/94abb95e3c9363afa8d35c23783959dadc43 Modified Files --

pgsql: Translation updates

2023-08-07 Thread Peter Eisentraut
Translation updates Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: 35f20e410919d90dd947e22d4ed99bb835efef0a Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/001561235787970ce91b60469498aac898dda866 Modified Files --

Re: pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread Tom Lane
David Rowley writes: > Don't Memoize lateral joins with volatile join conditions Is this really something to be pushing into stable branches less than 12 hours before a release wrap? We don't normally take such risks for anything but security patches, which this isn't. There will not, for examp

pgsql: Stamp 16beta3.

2023-08-07 Thread Tom Lane
Stamp 16beta3. Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0dd5545378d79bc0080dd34824f428458cf7448d Modified Files -- configure| 18 +- configure.ac | 2 +- meson.build | 2 +- 3 files changed, 11 insertions(+), 11 deletion

pgsql: Stamp 15.4.

2023-08-07 Thread Tom Lane
Stamp 15.4. Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/83ed1f71c88ae948a5b6ec6d2a4802cc54470102 Modified Files -- configure| 18 +- configure.ac | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-)

pgsql: Stamp 14.9.

2023-08-07 Thread Tom Lane
Stamp 14.9. Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/86648dcdaec67b83cec20a9d25b45ec089a7c624 Modified Files -- configure| 18 +- configure.ac | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-)

pgsql: Stamp 13.12.

2023-08-07 Thread Tom Lane
Stamp 13.12. Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c9d50b21a72d2bbc092ea9d7de4d4c044d8f8275 Modified Files -- configure| 18 +- configure.in | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-)

pgsql: Stamp 12.16.

2023-08-07 Thread Tom Lane
Stamp 12.16. Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/66c1983d96b66edbae1f1eb0070b447f128176e2 Modified Files -- configure| 18 +- configure.in | 2 +- src/include/pg_config.h.win32

pgsql: Stamp 11.21.

2023-08-07 Thread Tom Lane
Stamp 11.21. Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a2cbee74b0e174da7bcb441c142022216b9b266f Modified Files -- configure| 18 +- configure.in | 2 +- doc/bug.template

Re: pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread David Rowley
On Tue, 8 Aug 2023 at 01:02, Tom Lane wrote: > > David Rowley writes: > > Don't Memoize lateral joins with volatile join conditions > > Is this really something to be pushing into stable branches less than > 12 hours before a release wrap? We don't normally take such risks > for anything but sec

Re: pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread Tom Lane
David Rowley writes: > On Tue, 8 Aug 2023 at 01:02, Tom Lane wrote: >> Is this really something to be pushing into stable branches less than >> 12 hours before a release wrap? > My apologies. I had been under the impression that the go-no window > was between stamp and tag and *that* was the win

pgsql: doc: Fix incorrect entries generated from wait_event_names.txt

2023-08-07 Thread Michael Paquier
doc: Fix incorrect entries generated from wait_event_names.txt fa88928 has introduced wait_event_names.txt, and some of its entries had some documentation fields with more information than necessary. This commit brings back the description of all the wait events to be consistent with the older st

Re: pgsql: Don't Memoize lateral joins with volatile join conditions

2023-08-07 Thread David Rowley
On Tue, 8 Aug 2023 at 10:06, Tom Lane wrote: > > David Rowley writes: > > * https://wiki.postgresql.org/wiki/Committing_checklist > > I thought we had something written down there after the last > discussion of this point, but maybe it was hanging fire because > we hadn't chosen a specific defini