pgsql: Don't use INT64_FORMAT inside message strings

Don't use INT64_FORMAT inside message strings Use %lld and cast to long long int instead. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3286065651477c2060910dfb42b3cedbd79a7980 Modified Files -- src/bin/pg_rewind/libpq_source.c | 8 1 file cha

pgsql: doc: Improve hyphenation consistency

doc: Improve hyphenation consistency Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/544b28088f9d41750ccf193812da62bdfe4bd98a Modified Files -- doc/src/sgml/catalogs.sgml| 14 +++--- doc/src/sgml/ddl.sgml | 2 +

pgsql: Fix typo

Fix typo Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f0ec598b4323d8b29df5c67f2cd547a507ed Modified Files -- src/backend/access/transam/xlogprefetch.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: Use correct format placeholder for timeline IDs

Use correct format placeholder for timeline IDs Should be %u rather than %d. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/39d0928a0e88426ee64189898565c40d4af9ad96 Modified Files -- src/bin/pg_rewind/pg_rewind.c | 2 +- 1 file changed, 1 insertion(+),

pgsql: Add DISTINCT to information schema usage views

Add DISTINCT to information schema usage views Since pg_depend can contain duplicate entries, we need to eliminate those in information schema views that build on pg_depend, using DISTINCT. Some of the older views already did that correctly, but some of the more recently added ones didn't. (In s

Re: pgsql: Add DISTINCT to information schema usage views

On Wed, 21 Apr 2021 at 22:32, Peter Eisentraut wrote: > Add DISTINCT to information schema usage views What do you think of the idea of just getting rid of all these DISTINCTs and instead do a semi-join so that we don't get duplicate rows? For me, I don't really like the DISTINCTs as the behavio

pgsql: Only ever test for non-127.0.0.1 addresses on Windows in Postgre

Only ever test for non-127.0.0.1 addresses on Windows in PostgresNode This has been found to cause hangs where tcp usage is forced. Alexey Kodratov Discussion: https://postgr.es/m/[email protected] Backpatch to all live branches Branch -- REL9_6_STABLE Detail

pgsql: Only ever test for non-127.0.0.1 addresses on Windows in Postgre

Only ever test for non-127.0.0.1 addresses on Windows in PostgresNode This has been found to cause hangs where tcp usage is forced. Alexey Kodratov Discussion: https://postgr.es/m/[email protected] Backpatch to all live branches Branch -- REL_13_STABLE Detail

pgsql: Only ever test for non-127.0.0.1 addresses on Windows in Postgre

Only ever test for non-127.0.0.1 addresses on Windows in PostgresNode This has been found to cause hangs where tcp usage is forced. Alexey Kodratov Discussion: https://postgr.es/m/[email protected] Backpatch to all live branches Branch -- REL_10_STABLE Detail

pgsql: Only ever test for non-127.0.0.1 addresses on Windows in Postgre

Only ever test for non-127.0.0.1 addresses on Windows in PostgresNode This has been found to cause hangs where tcp usage is forced. Alexey Kodratov Discussion: https://postgr.es/m/[email protected] Backpatch to all live branches Branch -- REL_11_STABLE Detail

pgsql: Only ever test for non-127.0.0.1 addresses on Windows in Postgre

Only ever test for non-127.0.0.1 addresses on Windows in PostgresNode This has been found to cause hangs where tcp usage is forced. Alexey Kodratov Discussion: https://postgr.es/m/[email protected] Backpatch to all live branches Branch -- master Details -

pgsql: Only ever test for non-127.0.0.1 addresses on Windows in Postgre

Only ever test for non-127.0.0.1 addresses on Windows in PostgresNode This has been found to cause hangs where tcp usage is forced. Alexey Kodratov Discussion: https://postgr.es/m/[email protected] Backpatch to all live branches Branch -- REL_12_STABLE Detail

pgsql: Update config.guess and config.sub

Update config.guess and config.sub Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/26ac261ee4033710cad44f7924d53753129b60c7 Modified Files -- config/config.guess | 278 +-- config/config.sub | 643 +---

pgsql: fix silly perl error in commit d064afc720

fix silly perl error in commit d064afc720 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6cb7dcdb03d76f93411e0e810aba13b6fe4c9a43 Modified Files -- src/test/perl/PostgresNode.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

pgsql: fix silly perl error in commit d064afc720

fix silly perl error in commit d064afc720 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/e34adb2e6960ba8e885797a413620b344f468933 Modified Files -- src/test/perl/PostgresNode.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

pgsql: fix silly perl error in commit d064afc720

fix silly perl error in commit d064afc720 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/574a1b8fb42a9a74b84137a7600d561b4b2d48a4 Modified Files -- src/test/perl/PostgresNode.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

pgsql: fix silly perl error in commit d064afc720

fix silly perl error in commit d064afc720 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/246e9f0341ef6215c09f398ea90ae09abdf5d714 Modified Files -- src/test/perl/PostgresNode.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

pgsql: fix silly perl error in commit d064afc720

fix silly perl error in commit d064afc720 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/f7ac005c70588b8bedbe5f1a91848e0d1c9b258d Modified Files -- src/test/perl/PostgresNode.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

pgsql: fix silly perl error in commit d064afc720

fix silly perl error in commit d064afc720 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e014d25deade08df082d2b37de45adb0c984f563 Modified Files -- src/test/perl/PostgresNode.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

pgsql: Don't add a redundant constraint when detaching a partition

Don't add a redundant constraint when detaching a partition On ALTER TABLE .. DETACH CONCURRENTLY, we add a new table constraint that duplicates the partition constraint. But if the partition already has another constraint that implies that one, then that's unnecessary. We were already avoiding t

pgsql: Add comment about extract_autovac_opts not holding lock

Add comment about extract_autovac_opts not holding lock Per observation from Tom Lane. Discussion: https://postgr.es/m/[email protected] Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7c298c6573a0f181963ddcb40c850fa9c7da0ada Modified Files

pgsql: doc: Move parallel_leader_participation to its correct category

doc: Move parallel_leader_participation to its correct category parallel_leader_participation got introduced in e5253fd, where it was listed under RESOURCES_ASYNCHRONOUS in guc.c, but the documentation did not reflect that and listed it with the other planner-related options. This commit fixes th

pgsql: Fix relation leak for subscribers firing triggers in logical rep

Fix relation leak for subscribers firing triggers in logical replication Creating a trigger on a relation to which an apply operation is triggered would cause a relation leak once the change gets committed, as the executor would miss that the relation needs to be closed beforehand. This issue got