diff options
| author | Amit Kapila <akapila@postgresql.org> | 2025-09-15 08:44:54 +0000 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2025-09-15 08:46:55 +0000 |
| commit | 0d48d393d465b6f1abe18b86bd5ac2de0636a40e (patch) | |
| tree | 8c1a42ff5bc36afeee8c67365174b46866ee148f /doc/src | |
| parent | 282d0bdee6192f1a859ee34672ae73abf49794dc (diff) | |
Resume conflict-relevant data retention automatically.
This commit resumes automatic retention of conflict-relevant data for a
subscription. Previously, retention would stop if the apply process failed
to advance its xmin (oldest_nonremovable_xid) within the configured
max_retention_duration and user needs to manually re-enable
retain_dead_tuples option. With this change, retention will resume
automatically once the apply worker catches up and begins advancing its
xmin (oldest_nonremovable_xid) within the configured threshold.
Author: Zhijie Hou <houzj.fnst@fujitsu.com>
Reviewed-by: shveta malik <shveta.malik@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Reviewed-by: Dilip Kumar <dilipbalaut@gmail.com>
Reviewed-by: Masahiko Sawada <sawada.mshk@gmail.com>
Discussion: https://postgr.es/m/OS0PR01MB5716BE80DAEB0EE2A6A5D1F5949D2@OS0PR01MB5716.jpnprd01.prod.outlook.com
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/create_subscription.sgml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml index fc314437311..ed82cf1809e 100644 --- a/doc/src/sgml/ref/create_subscription.sgml +++ b/doc/src/sgml/ref/create_subscription.sgml @@ -538,10 +538,11 @@ CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceabl <literal>retain_dead_tuples</literal> is enabled, confirm that the retention duration has exceeded the <literal>max_retention_duration</literal> set within the corresponding - subscription. The retention will not be automatically resumed unless a - new subscription is created with <literal>retain_dead_tuples = - true</literal>, or the user manually re-enables - <literal>retain_dead_tuples</literal>. + subscription. The retention will automatically resume when at least one + apply worker confirms that the retention duration is within the + specified limit, or when a new subscription is created with + <literal>retain_dead_tuples = true</literal>. Alternatively, retention + can be manually resumed by re-enabling <literal>retain_dead_tuples</literal>. </para> <para> Note that overall retention will not stop if other subscriptions that |