Doc: Add the new section "Logical Replication Failover".
This aids the users to ensure that the failover marked slots are synced
to the standby and subscribers can continue replication even when the
publisher node goes down.
Author: Hou Zhijie, Shveta Malik, Amit Kapila
Reviewed-by: Peter Smith,
doc: Fix copy-and-paste mistake
The wording from the "columns" view was copied to the "attributes"
view without the required adjustments.
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/8d072feb9f6376b0a573f5d68df7dd944024c4b8
Modified Files
--
d
doc: Fix copy-and-paste mistake
The wording from the "columns" view was copied to the "attributes"
view without the required adjustments.
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/00071ef04ce08b8ac4168085c9d0fc3f685c825c
Modified Files
--
d
doc: Fix copy-and-paste mistake
The wording from the "columns" view was copied to the "attributes"
view without the required adjustments.
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9c4ce2da10551ae9fd695bb62494294b4ee07f95
Modified Files
--
d
doc: Fix copy-and-paste mistake
The wording from the "columns" view was copied to the "attributes"
view without the required adjustments.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4b8791743e0e2c7134ac915ad2aa01ecf6b6571e
Modified Files
--
doc/src/
doc: Fix copy-and-paste mistake
The wording from the "columns" view was copied to the "attributes"
view without the required adjustments.
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d9ff92c235226f68bbafcc8bb5260a8a51aedec1
Modified Files
--
d
doc: Fix copy-and-paste mistake
The wording from the "columns" view was copied to the "attributes"
view without the required adjustments.
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/788c23003f4c42d9114fa8e9881ccea870187da5
Modified Files
--
d
Collation documentation fixes.
Discussion:
https://postgr.es/m/[email protected]
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/8ba34c698d19450ccae9a5aea59a6d0bc8b75c0e
Modified Files
--
doc/src/sgml/catalogs.sgml | 1
meson: Add user-provided c_args to bitcode_cflags
This is needed for example to pass an include path set in the CPPFLAGS
environment variable to the bitcode compile command.
Discussion:
https://www.postgresql.org/message-id/flat/c1384a7b-ed12-4862-a0da-a05c7945171a%40eisentraut.org
Branch
-
Add meson NLS support for pg_walsummary
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b0f2659c7d9bdf3ccfdd1548dfecf602b901f507
Modified Files
--
src/bin/pg_walsummary/meson.build| 2 ++
src/bin/pg_walsummary/po/meson.build | 3 +++
2 files changed, 5
Fix failure with SQL-procedure polymorphic output arguments in v12.
Before the v13-era commit 913bbd88d, check_sql_fn_retval fails to
resolve polymorphic output types and then just throws up its hands and
assumes the check will be made at runtime. I think that's true for
ordinary functions return
Fix failure with SQL-procedure polymorphic output arguments in v12.
Before the v13-era commit 913bbd88d, check_sql_fn_retval fails to
resolve polymorphic output types and then just throws up its hands and
assumes the check will be made at runtime. I think that's true for
ordinary functions return
Fix failure with SQL-procedure polymorphic output arguments in v12.
Before the v13-era commit 913bbd88d, check_sql_fn_retval fails to
resolve polymorphic output types and then just throws up its hands and
assumes the check will be made at runtime. I think that's true for
ordinary functions return
Fix failure with SQL-procedure polymorphic output arguments in v12.
Before the v13-era commit 913bbd88d, check_sql_fn_retval fails to
resolve polymorphic output types and then just throws up its hands and
assumes the check will be made at runtime. I think that's true for
ordinary functions return
Fix failure with SQL-procedure polymorphic output arguments in v12.
Before the v13-era commit 913bbd88d, check_sql_fn_retval fails to
resolve polymorphic output types and then just throws up its hands and
assumes the check will be made at runtime. I think that's true for
ordinary functions return
Fix failure with SQL-procedure polymorphic output arguments in v12.
Before the v13-era commit 913bbd88d, check_sql_fn_retval fails to
resolve polymorphic output types and then just throws up its hands and
assumes the check will be made at runtime. I think that's true for
ordinary functions return
Make RelationFlushRelation() work without ResourceOwner during abort
ReorderBufferImmediateInvalidation() executes invalidation messages in
an aborted transaction. However, RelationFlushRelation sometimes
required a valid resource owner, to temporarily increment the refcount
of the relache entry.
Fix asymmetry in setting EquivalenceClass.ec_sortref
0452b461bc made get_eclass_for_sort_expr() always set
EquivalenceClass.ec_sortref if it's not done yet. This leads to an asymmetric
situation when whoever first looks for the EquivalenceClass sets the
ec_sortref. It is also counterintuitive th
Add invariants check to get_useful_group_keys_orderings()
This commit introduces invariants checking of generated orderings
in get_useful_group_keys_orderings() for assert-enabled builds.
Discussion:
https://postgr.es/m/a663f0f6-cbf6-49aa-af2e-234dc6768a07%40postgrespro.ru
Reported-by: Tom Lane
Rename PathKeyInfo to GroupByOrdering
0452b461bc made optimizer explore alternative orderings of group-by pathkeys.
The PathKeyInfo data structure was used to store the particular ordering of
group-by pathkeys and corresponding clauses. It turns out that PathKeyInfo
is not the best name for that
Restore preprocess_groupclause()
0452b461bc made optimizer explore alternative orderings of group-by pathkeys.
It eliminated preprocess_groupclause(), which was intended to match items
between GROUP BY and ORDER BY. Instead, get_useful_group_keys_orderings()
function generates orderings of GROUP
21 matches
Mail list logo
