pgsql: doc PG 18 relnotes: adjust CREATE SUBSCRIPTION attribution

doc PG 18 relnotes: adjust CREATE SUBSCRIPTION attribution Reported-by: vignesh C Discussion: https://postgr.es/m/CALDaNm0Wy-vJ6dE+e=y=yuq31i2kvgf-rs-u6qog4k7tpu_...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/883339c170d1c73162283506c85536f735

pgsql: doc PG 18 relnotes: clarify btree skip scan item

doc PG 18 relnotes: clarify btree skip scan item Reported-by: Peter Geoghegan Discussion: https://postgr.es/m/CAH2-Wz=2CWXgO1+uyR-VfN3ALMtFnfTtXK-VtkoQQ89ogm=4...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7ddfac79f2cd315314efb1402e896fa4386a1

pgsql: doc PG 18 relnotes: remove duplicate commit entry

doc PG 18 relnotes: remove duplicate commit entry Item related to btree skip scans. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3b7140d27e248171fc4a9a18bdfd2288054e8bde Modified Files -- doc/src/sgml/release-18.sgml | 3 --- 1 file changed, 3 deleti

pgsql: Fix assorted new memory leaks in libpq.

Fix assorted new memory leaks in libpq. Valgrind'ing the postgres_fdw tests showed me that libpq was leaking PGconn.be_cancel_key. It looks like freePGconn is expecting pqDropServerData to release it ... but in a cancel connection object, that doesn't happen. Looking a little closer, I was disma

pgsql: Replace deprecated log_connections values in docs and tests

Replace deprecated log_connections values in docs and tests 9219093cab2607f modularized log_connections output to allow more granular control over which aspects of connection establishment are logged. It converted the boolean log_connections GUC into a list of strings and deprecated previously sup

pgsql: In ExecInitModifyTable, don't scribble on the source plan.

In ExecInitModifyTable, don't scribble on the source plan. The code carelessly modified mtstate->ps.plan->targetlist, which it's not supposed to do. Fortunately, there's not really any need to do that because the planner already set up a perfectly acceptable targetlist for the plan node. We just

pgsql: Fix memory leak in XMLSERIALIZE(... INDENT).

Fix memory leak in XMLSERIALIZE(... INDENT). xmltotext_with_options sometimes tries to replace the existing root node of a libxml2 document. In that case xmlDocSetRootElement will unlink and return the old root node; if we fail to free it, it's leaked for the remainder of the session. The amount

pgsql: Fix memory leak in XMLSERIALIZE(... INDENT).

Fix memory leak in XMLSERIALIZE(... INDENT). xmltotext_with_options sometimes tries to replace the existing root node of a libxml2 document. In that case xmlDocSetRootElement will unlink and return the old root node; if we fail to free it, it's leaked for the remainder of the session. The amount

pgsql: Fix memory leak in XMLSERIALIZE(... INDENT).

Fix memory leak in XMLSERIALIZE(... INDENT). xmltotext_with_options sometimes tries to replace the existing root node of a libxml2 document. In that case xmlDocSetRootElement will unlink and return the old root node; if we fail to free it, it's leaked for the remainder of the session. The amount

pgsql: pg_dump: Adjust reltuples from 0 to -1 for dumps of older versio

pg_dump: Adjust reltuples from 0 to -1 for dumps of older versions. Before v14, a reltuples value of 0 was ambiguous: it could either mean the relation is empty, or it could mean that it hadn't yet been vacuumed or analyzed. (Commit 3d351d916b taught v14 and newer to use -1 for the latter case.)

pgsql: Remove accidentally added meson.build

Remove accidentally added meson.build Commit b4363fc66e6 added an empty meson.build to 13, presumably due to a conflict resolution while backpatching. Remove it. Discussion: https://postgr.es/m/b7angm4wz2ln2wsqvsb3bwl4pqa4xxgcawn36o5kweu5pgpl6s@ofhhrgl5ouwb Branch -- REL_13_STABLE Details

GSS Auth issue when user member of lots of AD groups

Hi, GSS authentication is working for users with small number of AD groups but getting below error when a user has larger number of groups. I believe it might to token size related, but they don't have issues when authenticating with Kerberos/GSS to other applications, only with Postgres. fail

pgsql: Revert "Don't lock partitions pruned by initial pruning"

Revert "Don't lock partitions pruned by initial pruning" As pointed out by Tom Lane, the patch introduced fragile and invasive design around plan invalidation handling when locking of prunable partitions was deferred from plancache.c to the executor. In particular, it violated assumptions about Ca