pgsql: Prevent tuples to be marked as dead in subtransactions on standb

Prevent tuples to be marked as dead in subtransactions on standbys Dead tuples are ignored and are not marked as dead during recovery, as it can lead to MVCC issues on a standby because its xmin may not match with the primary. This information is tracked by a field called "xactStartedInRecovery"

pgsql: Prevent tuples to be marked as dead in subtransactions on standb

Prevent tuples to be marked as dead in subtransactions on standbys Dead tuples are ignored and are not marked as dead during recovery, as it can lead to MVCC issues on a standby because its xmin may not match with the primary. This information is tracked by a field called "xactStartedInRecovery"

pgsql: Prevent tuples to be marked as dead in subtransactions on standb

Prevent tuples to be marked as dead in subtransactions on standbys Dead tuples are ignored and are not marked as dead during recovery, as it can lead to MVCC issues on a standby because its xmin may not match with the primary. This information is tracked by a field called "xactStartedInRecovery"

pgsql: Prevent tuples to be marked as dead in subtransactions on standb

Prevent tuples to be marked as dead in subtransactions on standbys Dead tuples are ignored and are not marked as dead during recovery, as it can lead to MVCC issues on a standby because its xmin may not match with the primary. This information is tracked by a field called "xactStartedInRecovery"

pgsql: Prevent tuples to be marked as dead in subtransactions on standb

Prevent tuples to be marked as dead in subtransactions on standbys Dead tuples are ignored and are not marked as dead during recovery, as it can lead to MVCC issues on a standby because its xmin may not match with the primary. This information is tracked by a field called "xactStartedInRecovery"

pgsql: Prevent tuples to be marked as dead in subtransactions on standb

Prevent tuples to be marked as dead in subtransactions on standbys Dead tuples are ignored and are not marked as dead during recovery, as it can lead to MVCC issues on a standby because its xmin may not match with the primary. This information is tracked by a field called "xactStartedInRecovery"

pgsql: Fix typo in comment

Fix typo in comment Commit 98e675ed7af accidentally mistyped IDENTIFY_SYSTEM as IDENTIFY_SERVER. Backpatch to all supported branches. Reported-by: Alexander Lakhin Discussion: https://postgr.es/m/68138521-5345-8780-4390-1474afdcb...@gmail.com Branch -- REL_12_STABLE Details ---

pgsql: Fix typo in comment

Fix typo in comment Commit 98e675ed7af accidentally mistyped IDENTIFY_SYSTEM as IDENTIFY_SERVER. Backpatch to all supported branches. Reported-by: Alexander Lakhin Discussion: https://postgr.es/m/68138521-5345-8780-4390-1474afdcb...@gmail.com Branch -- REL_13_STABLE Details ---

pgsql: Fix typo in comment

Fix typo in comment Commit 98e675ed7af accidentally mistyped IDENTIFY_SYSTEM as IDENTIFY_SERVER. Backpatch to all supported branches. Reported-by: Alexander Lakhin Discussion: https://postgr.es/m/68138521-5345-8780-4390-1474afdcb...@gmail.com Branch -- REL_14_STABLE Details ---

pgsql: Fix typo in comment

Fix typo in comment Commit 98e675ed7af accidentally mistyped IDENTIFY_SYSTEM as IDENTIFY_SERVER. Backpatch to all supported branches. Reported-by: Alexander Lakhin Discussion: https://postgr.es/m/68138521-5345-8780-4390-1474afdcb...@gmail.com Branch -- REL_15_STABLE Details ---

pgsql: Fix typo in comment

Fix typo in comment Commit 98e675ed7af accidentally mistyped IDENTIFY_SYSTEM as IDENTIFY_SERVER. Backpatch to all supported branches. Reported-by: Alexander Lakhin Discussion: https://postgr.es/m/68138521-5345-8780-4390-1474afdcb...@gmail.com Branch -- REL_16_STABLE Details ---

pgsql: Fix typo in comment

Fix typo in comment Commit 98e675ed7af accidentally mistyped IDENTIFY_SYSTEM as IDENTIFY_SERVER. Backpatch to all supported branches. Reported-by: Alexander Lakhin Discussion: https://postgr.es/m/68138521-5345-8780-4390-1474afdcb...@gmail.com Branch -- master Details ---