pgsql: Stamp 13.22.

Stamp 13.22. Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/af2dbe860b638dbd45604270d103e0a59dc0a372 Modified Files -- configure| 18 +- configure.in | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-)

pgsql: Stamp 14.19.

Stamp 14.19. Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4e9da016ade3e75400f6fdc22ed1fed7fdd32f7a Modified Files -- configure| 18 +- configure.ac | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-)

pgsql: Stamp 15.14.

Stamp 15.14. Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0ab43b548237b3791261480d6a023f6b95b53942 Modified Files -- configure| 18 +- configure.ac | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-)

pgsql: Stamp 16.10.

Stamp 16.10. Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c13dd7d50f21268dc64b4b3edbce31993985ab12 Modified Files -- configure| 18 +- configure.ac | 2 +- meson.build | 2 +- 3 files changed, 11 insertions(+), 11 deletions(

pgsql: Stamp 17.6.

Stamp 17.6. Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7885b94dd81b98bbab9ed878680d156df7bf857f Modified Files -- configure| 18 +- configure.ac | 2 +- meson.build | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-

pgsql: Stamp 18beta3.

Stamp 18beta3. Branch -- REL_18_STABLE Details --- https://git.postgresql.org/pg/commitdiff/ab844ce378fe81d15cf000f821af663af3846ab6 Modified Files -- configure| 18 +- configure.ac | 2 +- meson.build | 2 +- 3 files changed, 11 insertions(+), 11 deletion

pgsql: Release notes for 17.6, 16.10, 15.14, 14.19, 13.22.

Release notes for 17.6, 16.10, 15.14, 14.19, 13.22. Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/94c067376d5395fff7bf3e7980d11fcd2482b2be Modified Files -- doc/src/sgml/release-16.sgml | 1434 ++ 1 file ch

pgsql: Release notes for 17.6, 16.10, 15.14, 14.19, 13.22.

Release notes for 17.6, 16.10, 15.14, 14.19, 13.22. Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/dfe189ecdf8709b332439ae72693d10b2640234b Modified Files -- doc/src/sgml/release-15.sgml | 1336 ++ 1 file ch

pgsql: Release notes for 17.6, 16.10, 15.14, 14.19, 13.22.

Release notes for 17.6, 16.10, 15.14, 14.19, 13.22. Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e21c9823d387a31d9efe452fff60a88f3c4a7e19 Modified Files -- doc/src/sgml/release-14.sgml | 1209 ++ 1 file ch

pgsql: Release notes for 17.6, 16.10, 15.14, 14.19, 13.22.

Release notes for 17.6, 16.10, 15.14, 14.19, 13.22. Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7ee1a7f89b65815001ce4a97570726ebbc988283 Modified Files -- doc/src/sgml/release-13.sgml | 1135 ++ 1 file ch

pgsql: Release notes for 17.6, 16.10, 15.14, 14.19, 13.22.

Release notes for 17.6, 16.10, 15.14, 14.19, 13.22. Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/024123a0d38e3f3fdcbab411eb01cba4b36adc86 Modified Files -- doc/src/sgml/release-17.sgml | 8 1 file changed, 8 insertions(+)

pgsql: Mop-up for Datum conversion cleanups.

Mop-up for Datum conversion cleanups. Fix a couple more places where an explicit Datum conversion is needed (not clear how we missed these in ff89e182d and previous commits). Replace the minority usage "(Datum) NULL" with "(Datum) 0". The former depends on the assumption that Datum is the same wi

pgsql: First-draft release notes for 17.6.

First-draft release notes for 17.6. As usual, the release notes for other branches will be made by cutting these down, but put them up for community review first. Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/b70d9de77f337828ca3a0a3064a6827b1ce68977 Modifi

Re: pgsql: oauth: Add unit tests for multiplexer handling

be advisable to keep the "clean" target doing its thing. But I agree with disabling 'all', 'check', 'installcheck'. regards, tom lane

Re: pgsql: oauth: Add unit tests for multiplexer handling

to short-circuit building the test program. I think the issue is that we apply that short-circuit at the next makefile level up --- can we do it in src/interfaces/libpq-oauth/Makefile itself? regards, tom lane

Re: pgsql: oauth: Add unit tests for multiplexer handling

g to build it anyway. regards, tom lane

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/04b7ff3cd33c0b9574eed3b662

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/fe966e886ce844fda218

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/186bc0dfdcb0d4376ffe

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/13244ba1032573bf1a22

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- REL_18_STABLE Details --- https://git.postgresql.org/pg/commitdiff/31c09ef4563612467b31

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/3a3b1d7ab1809910e51c

pgsql: doc: add float as an alias for double precision.

y: alexander.kj...@hafslund.no Author: Euler Taveira Reviewed-by: Tom Lane Discussion: https://postgr.es/m/175456294638.800.12038559679827947...@wrigleys.postgresql.org Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f9b09fe63cbc88319de7

pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric

of field complaints. However, users with BRIN indexes that use the numeric_minmax_multi_ops opclass may wish to reindex in hopes of making their indexes more efficient. Author: Peter Eisentraut Co-authored-by: Tom Lane Discussion: https://postgr.es/m/2093712.1753983...@sss.pgh.pa.us

pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric

of field complaints. However, users with BRIN indexes that use the numeric_minmax_multi_ops opclass may wish to reindex in hopes of making their indexes more efficient. Author: Peter Eisentraut Co-authored-by: Tom Lane Discussion: https://postgr.es/m/2093712.1753983...@sss.pgh.pa.us

pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric

of field complaints. However, users with BRIN indexes that use the numeric_minmax_multi_ops opclass may wish to reindex in hopes of making their indexes more efficient. Author: Peter Eisentraut Co-authored-by: Tom Lane Discussion: https://postgr.es/m/2093712.1753983...@sss.pgh.pa.us

pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric

of field complaints. However, users with BRIN indexes that use the numeric_minmax_multi_ops opclass may wish to reindex in hopes of making their indexes more efficient. Author: Peter Eisentraut Co-authored-by: Tom Lane Discussion: https://postgr.es/m/2093712.1753983...@sss.pgh.pa.us

pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric

of field complaints. However, users with BRIN indexes that use the numeric_minmax_multi_ops opclass may wish to reindex in hopes of making their indexes more efficient. Author: Peter Eisentraut Co-authored-by: Tom Lane Discussion: https://postgr.es/m/2093712.1753983...@sss.pgh.pa.us

pgsql: Fix incorrect return value in brin_minmax_multi_distance_numeric

of field complaints. However, users with BRIN indexes that use the numeric_minmax_multi_ops opclass may wish to reindex in hopes of making their indexes more efficient. Author: Peter Eisentraut Co-authored-by: Tom Lane Discussion: https://postgr.es/m/2093712.1753983...@sss.pgh.pa.us

pgsql: Mop-up for commit e035863c9.

Mop-up for commit e035863c9. Neither Peter nor I had tried this with USE_VALGRIND ... Per buildfarm member skink. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f291751ef86ec407b3e67a951f55e79fb160ae10 Modified Files -- src/backend/access/common/print

pgsql: Take a little more care in set_backtrace().

Take a little more care in set_backtrace(). Coverity complained that the "errtrace" string is leaked if we return early because backtrace_symbols fails. Another criticism that could be leveled at this is that not providing any hint of what happened is user-unfriendly. Fix that. The odds of a le

pgsql: Silence Valgrind leakage complaints in more-or-less-hackish ways

s socket-files and lock-files lists being leaked, which we can silence by just not nulling out the static pointers to them. * Valgrind seems not to consider the global "environ" variable as a valid root pointer; so when we allocate a new environment array, it claims that data is leaked.

pgsql: Silence complaints about leaks in PlanCacheComputeResultDesc.

27;t provoking Valgrind complaints. (Perhaps in a CLOBBER_CACHE_ALWAYS build, they would?) For the moment, this makes the src/pl/plpgsql tests leak-free according to Valgrind. Author: Tom Lane Reviewed-by: Andres Freund Discussion: https://postgr.es/m/285483.1746756...@sss.pgh.pa.us Branch

pgsql: Suppress complaints about leaks in TS dictionary loading.

ing to fix this completely. However, I did grab some low-hanging fruit: several places were leaking the result of get_tsearch_config_filename. This seems worth doing mostly because they are inconsistent with other dictionaries that were freeing it already. Author: Tom Lane Reviewed-by: And

pgsql: Avoid leakage of zero-length arrays in partition_bounds_copy().

hich do say "0 bytes lost". Author: Tom Lane Discussion: https://postgr.es/m/285483.1746756...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4fbfdde58e4cd091f88737dffa241b08c23d8829 Modified Files -- src/backend/

pgsql: Fix assorted pretty-trivial memory leaks in the backend.

r that code out into a helper function. define_custom_variable's logic was one brick shy of a load too: it forgot to free the separate allocation for the placeholder's name. Author: Tom Lane Reviewed-by: Andres Freund Reviewed-by: Richard Guo Discussion: https://pos

pgsql: Fix MemoryContextAllocAligned's interaction with Valgrind.

nstead of rolling its own implementation, which was equally broken according to Valgrind. Author: Tom Lane Reviewed-by: Andres Freund Discussion: https://postgr.es/m/285483.1746756...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/9e9190154ef204a4e814dcc99f76339

pgsql: Improve our support for Valgrind's leak tracking.

elpful to start with the comments added at the head of mcxt.c. Author: Andres Freund Co-authored-by: Tom Lane Discussion: https://postgr.es/m/285483.1746756...@sss.pgh.pa.us Discussion: https://postgr.es/m/20210317181531.7oggpqevzz6bk...@alap3.anarazel.de Branch -

pgsql: Reduce leakage during PL/pgSQL function compilation.

e far from the only leaks in PL/pgSQL compilation, but they're the biggest as far as I've seen, and further improvement looks like it'd require delicate and bug-prone surgery. Author: Tom Lane Reviewed-by: Andres Freund Discussion: https://postgr.es/m/285483.1746756...@sss.pgh.pa

pgsql: Suppress complaints about leaks in function cache loading.

cases because we're unsure if any fn_extra pointers remain. That might be nice to do something about eventually, but it's not clear how. Author: Tom Lane Reviewed-by: Andres Freund Discussion: https://postgr.es/m/285483.1746756...@sss.pgh.pa.us Branch -- master Details ---

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- REL_18_STABLE Details --- https://git.postgresql.org/pg/commitdiff/8e5e3ff5564104b5e1c3c

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/bbc20c8a9ffdefcabd70e

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/19857437b07353908c7da

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c5bd803e58162e39e3dcd

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a644f5fc66a36ff7c630b

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4300d8b6a79d61abb5ca9

pgsql: Don't put library-supplied -L/-I switches before user-supplied o

to someone else to investigate that. Reported-by: Charles Samborski Author: Tom Lane Discussion: https://postgr.es/m/70f2155f-27ca-4534-b33d-7750e2063...@demurgos.net Backpatch-through: 13 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/2dee95bd0cf18d99e4d47

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- REL_18_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- master Details --- https://git.postgresql.org/pg/

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

ssentially completes reverting all the non-cosmetic changes in 6082b3d5d.) Reported-by: Jim Jones Author: Tom Lane Discussion: https://postgr.es/m/997668.1753802...@sss.pgh.pa.us Backpatch-through: 13 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Split up pgfdw_report_error so that we can mark it pg_noreturn.

atching any harder than it was already. Author: Tom Lane Discussion: https://postgr.es/m/420221.1753714...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/74e121c8dc5184318478dee587cf7d8303ab1357 Modified Files -- contrib/po

pgsql: Suppress uninitialized-variable warning.

at the previous presence of a setjmp() in the function stopped them from attempting any flow analysis at all. Add a dummy initialization to silence the warning. Reported-by: Ashutosh Bapat Author: Tom Lane Discussion: https://postgr.es/m/caexhw5tkercufa_f6oct5dmj61n+yvrvgyxl7m8dd-5_zxj...@mail.gm

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/71c0921b649d7a800eb2d6f9353989

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- REL_18_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Avoid regression in the size of XML input that we will accept.

eported-by: Michael Paquier Author: Michael Paquier Co-authored-by: Erik Wienhold Reviewed-by: Tom Lane Discussion: https://postgr.es/m/aigknluc8b8eg...@paquier.xyz Backpatch-through: 13 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/

pgsql: Add commit 73873805f to .git-blame-ignore-revs.

Add commit 73873805f to .git-blame-ignore-revs. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/db6461b1c9aae122b90bb52430f06efb306b371a Modified Files -- .git-blame-ignore-revs | 3 +++ 1 file changed, 3 insertions(+)

pgsql: Run pgindent on the changes of the previous patch.

Run pgindent on the changes of the previous patch. This step can be checked mechanically. Author: Tom Lane Reviewed-by: Matheus Alcantara Discussion: https://postgr.es/m/2976982.1748049...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.org/pg/commitdiff

pgsql: Create infrastructure to reliably prevent leakage of PGresults.

of this mechanism. A good deal of follow-on simplification is possible now that we don't have to be so cautious about freeing PGresults, but I'll put that in a separate patch. Author: Tom Lane Reviewed-by: Matheus Alcantara Discussion: https://postgr.es/m/2976982.1748049...@sss.p

pgsql: Reap the benefits of not having to avoid leaking PGresults.

did not re-indent code within the removed PG_TRY constructs. That'll be done in a separate patch. Author: Tom Lane Reviewed-by: Matheus Alcantara Discussion: https://postgr.es/m/2976982.1748049...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.org/pg/commi

pgsql: Silence leakage complaint about postgres_fdw's InitPgFdwOptions.

ch seems like a pretty negligible cost in a function that runs at most once per process. Author: Tom Lane Reviewed-by: Matheus Alcantara Discussion: https://postgr.es/m/2976982.1748049...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.or

pgsql: Fix dynahash's HASH_FIXED_SIZE ("isfixed") option.

This oversight dates to 7c797e719 which invented the option. But back-patching doesn't seem appropriate given the lack of field complaints. If there is anyone running an affected workload on Windows, they might be unhappy about the behavior changing in a minor release. Author: Aidar Imamov

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- REL_13_STA

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- REL_15_STA

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- REL_18_STA

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- master Detail

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- REL_16_STA

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- REL_17_STA

pgsql: Fix build breakage on Solaris-alikes with late-model GCC.

use that same symbol to control whether we include "const" in the declaration of pam_passwd_conv_proc(). Bug: #18995 Reported-by: Andrew Watkins Author: Tom Lane Discussion: https://postgr.es/m/18995-82058da9ab433...@postgresql.org Backpatch-through: 13 Branch -- REL_14_STA

pgsql: Mostly-cosmetic adjustments to estimate_multivariate_bucketsize(

s way, especially if we take the opportunity to add some comments so that readers don't have to reverse-engineer the usage of these local variables. Also add some braces for better/more consistent style. Author: Tender Wang Reviewed-by: Tom Lane Discussion: https://postgr.es/m/CAHewX

pgsql: Speed up byteain by not parsing traditional-style input twice.

d byteaout. Author: Steven Niu Reviewed-by: Kirill Reshke Reviewed-by: Stepan Neretin Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca315729-140b-426e-81a6-6cd5cfe7e...@gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3683af617044d271ab7486d43d06f9

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- REL_15_STABLE Details --- https://git.po

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- master Details --- https://git.po

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.po

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- REL_17_STABLE Details --- https://git.po

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- REL_18_STABLE Details --- https://git.po

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- REL_14_STABLE Details --- https://git.po

pgsql: Fix PQport to never return NULL unless the connection is NULL.

nd master do that. Author: Daniele Varrazzo Reviewed-by: Laurenz Albe Reviewed-by: Tom Lane Discussion: https://postgr.es/m/ca+mi_8yts8wpzpo0pab2aaglwhuq0deqrf0zmnvwss4y9fw...@mail.gmail.com Backpatch-through: 13 Branch -- REL_16_STABLE Details --- https://git.po

Re: pgsql: pg_logicalinspect: Fix possible crash when passing a directory p

David Rowley writes: > On Thu, 17 Jul 2025 at 15:19, Tom Lane wrote: >> Hmph. I doubt we are ready to require C11 everywhere, but maybe >> we could require it in MSVC builds? Which MSVC versions would >> that eliminate? > Going by [1] it's Visual Studio 2019, whi

Re: pgsql: pg_logicalinspect: Fix possible crash when passing a directory p

David Rowley writes: > On Thu, 17 Jul 2025 at 02:56, Tom Lane wrote: >> Looking again at the code for ereport_domain(), I wondered if >> something like this would help MSVC see through it: > I tried this and it unfortunately doesn't fix the issue. I didn't have hug

Re: pgsql: pg_logicalinspect: Fix possible crash when passing a directory p

er thinks is_error_ is a compile-time constant. I'm just guessing though, don't have this compiler to test with. regards, tom lane

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Doc: clarify description of regexp fields in pg_ident.conf.

E". Back-patch appropriate subsets. I did not risk changing pg_ident.conf.sample in released branches, but it still seems OK to change it in v18. Reported-by: Alexey Shishkin Author: Tom Lane Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/175206279327.31575

pgsql: Clarify the ra != rb case in compareJsonbContainers().

etely fails to explain this, and the Asserts don't cover it either. The comment is pretty obscure anyway, so rewrite it, and extend the Asserts to reject WJB_DONE. This is only cosmetic, so no need for back-patch. Author: Tom Lane Discussion: https://postgr.es/m/0c623e8a204187b87b4

pgsql: Silence uninitialized-value warnings in compareJsonbContainers()

n. Let's fix it in a less magical, more future-proof way by changing JsonbIteratorNext() so that it always does set val->type. The cost of that should be pretty negligible, and it makes the function's API spec less squishy. Reported-by: Erik Rijkers Author: Tom Lane Reviewed-by: Andr

pgsql: Silence uninitialized-value warnings in compareJsonbContainers()

n. Let's fix it in a less magical, more future-proof way by changing JsonbIteratorNext() so that it always does set val->type. The cost of that should be pretty negligible, and it makes the function's API spec less squishy. Reported-by: Erik Rijkers Author: Tom Lane Reviewed-by: Andr

pgsql: Silence uninitialized-value warnings in compareJsonbContainers()

n. Let's fix it in a less magical, more future-proof way by changing JsonbIteratorNext() so that it always does set val->type. The cost of that should be pretty negligible, and it makes the function's API spec less squishy. Reported-by: Erik Rijkers Author: Tom Lane Reviewed-by: Andr

pgsql: Silence uninitialized-value warnings in compareJsonbContainers()

n. Let's fix it in a less magical, more future-proof way by changing JsonbIteratorNext() so that it always does set val->type. The cost of that should be pretty negligible, and it makes the function's API spec less squishy. Reported-by: Erik Rijkers Author: Tom Lane Reviewed-by: Andr

  1   2   3   4   5   6   7   8   9   10   >