pgsql: Fix memory leak in pgoutput for the WAL sender

Fix memory leak in pgoutput for the WAL sender RelationSyncCache, the hash table in charge of tracking the relation schemas sent through pgoutput, was forgetting to free the TupleDesc associated to the two slots used to store the new and old tuples, causing some memory to be leaked each time a rel

pgsql: Fix memory leak in pgoutput for the WAL sender

Fix memory leak in pgoutput for the WAL sender RelationSyncCache, the hash table in charge of tracking the relation schemas sent through pgoutput, was forgetting to free the TupleDesc associated to the two slots used to store the new and old tuples, causing some memory to be leaked each time a rel

pgsql: Fix memory leak in pgoutput for the WAL sender

Fix memory leak in pgoutput for the WAL sender RelationSyncCache, the hash table in charge of tracking the relation schemas sent through pgoutput, was forgetting to free the TupleDesc associated to the two slots used to store the new and old tuples, causing some memory to be leaked each time a rel

pgsql: Fix memory leak in pgoutput for the WAL sender

Fix memory leak in pgoutput for the WAL sender RelationSyncCache, the hash table in charge of tracking the relation schemas sent through pgoutput, was forgetting to free the TupleDesc associated to the two slots used to store the new and old tuples, causing some memory to be leaked each time a rel

pgsql: doc: clarify that jsonb_path_match() returns an SQL boolean

doc: clarify that jsonb_path_match() returns an SQL boolean Not a JSON boolean. Also clarify that other predicate check expressions functions return a JSON boolean, not an SQL boolean. Reported-by: jian he Discussion: https://postgr.es/m/CACJufxH7tP1NXCHN1bUBXcEB=dv7-qe+zjb3uxwk6em+9qz...@mai

pgsql: More logically order libpq func. includes, e.g., group GUC vals

More logically order libpq func. includes, e.g., group GUC vals Reported-by: David Zhang Discussion: https://postgr.es/m/65909efe-97c6-4863-af4e-21eb5a26d...@highgo.ca Co-authored-by: David Zhang Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/comm

pgsql: doc: clarify that jsonb_path_match() returns an SQL boolean

doc: clarify that jsonb_path_match() returns an SQL boolean Not a JSON boolean. Also clarify that other predicate check expressions functions return a JSON boolean, not an SQL boolean. Reported-by: jian he Discussion: https://postgr.es/m/CACJufxH7tP1NXCHN1bUBXcEB=dv7-qe+zjb3uxwk6em+9qz...@mai

pgsql: clarify --no-comments option in --help and SGML files

clarify --no-comments option in --help and SGML files The previous commit, b38bac26e20, missed these cases for dump/restore. Reported-by: Tom Lane Discussion: https://postgr.es/m/3495698.1731968...@sss.pgh.pa.us Backpatch-through: master Branch -- master Details --- https://git.postgr

pgsql: Refine nbtree = redundancy preprocessing comment.

Refine nbtree = redundancy preprocessing comment. Spell out how a = key associated with a SAOP array renders a > key against the same index column redundant at the relevant point inside _bt_preprocess_keys. Follow-up to commit 5bf748b8. Branch -- master Details --- https://git.postgresq

pgsql: Avoid assertion failure if a setop leaf query contains setops.

Avoid assertion failure if a setop leaf query contains setops. Ordinarily transformSetOperationTree will collect all UNION/ INTERSECT/EXCEPT steps into the setOperations tree of the topmost Query, so that leaf queries do not contain any setOperations. However, it cannot thus flatten a subquery tha

pgsql: Avoid assertion failure if a setop leaf query contains setops.

Avoid assertion failure if a setop leaf query contains setops. Ordinarily transformSetOperationTree will collect all UNION/ INTERSECT/EXCEPT steps into the setOperations tree of the topmost Query, so that leaf queries do not contain any setOperations. However, it cannot thus flatten a subquery tha

pgsql: Avoid assertion failure if a setop leaf query contains setops.

Avoid assertion failure if a setop leaf query contains setops. Ordinarily transformSetOperationTree will collect all UNION/ INTERSECT/EXCEPT steps into the setOperations tree of the topmost Query, so that leaf queries do not contain any setOperations. However, it cannot thus flatten a subquery tha

pgsql: Avoid assertion failure if a setop leaf query contains setops.

Avoid assertion failure if a setop leaf query contains setops. Ordinarily transformSetOperationTree will collect all UNION/ INTERSECT/EXCEPT steps into the setOperations tree of the topmost Query, so that leaf queries do not contain any setOperations. However, it cannot thus flatten a subquery tha

pgsql: Avoid assertion failure if a setop leaf query contains setops.

Avoid assertion failure if a setop leaf query contains setops. Ordinarily transformSetOperationTree will collect all UNION/ INTERSECT/EXCEPT steps into the setOperations tree of the topmost Query, so that leaf queries do not contain any setOperations. However, it cannot thus flatten a subquery tha

pgsql: Avoid assertion failure if a setop leaf query contains setops.

Avoid assertion failure if a setop leaf query contains setops. Ordinarily transformSetOperationTree will collect all UNION/ INTERSECT/EXCEPT steps into the setOperations tree of the topmost Query, so that leaf queries do not contain any setOperations. However, it cannot thus flatten a subquery tha

pgsql: file_fdw: Add REJECT_LIMIT option to file_fdw.

file_fdw: Add REJECT_LIMIT option to file_fdw. Commit 4ac2a9bece introduced the REJECT_LIMIT option for the COPY command. This commit extends the support for this option to file_fdw. As well as REJECT_LIMIT option for COPY, this option limits the maximum number of erroneous rows that can be skipp

pgsql: Tag refs/tags/REL_14_15 was created

Tag refs/tags/REL_14_15 was created.

pgsql: Tag refs/tags/REL_13_18 was created

Tag refs/tags/REL_13_18 was created.

pgsql: Tag refs/tags/REL_15_10 was created

Tag refs/tags/REL_15_10 was created.