diff options
| author | Amit Kapila <akapila@postgresql.org> | 2025-05-19 11:04:39 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2025-05-19 11:04:39 +0530 |
| commit | e323d9df002debb103a58ba2479368c46804a9b6 (patch) | |
| tree | f19da752d505bb5b1ca64971fc40718d8b9e67c7 /src/backend/utils/adt | |
| parent | 9bc2d37ccaab206c9140b06b535280ed82e9fe49 (diff) | |
Don't retreat slot's confirmed_flush LSN.
Prevent moving the confirmed_flush backwards, as this could lead to data
duplication issues caused by replicating already replicated changes.
This can happen when a client acknowledges an LSN it doesn't have to do
anything for, and thus didn't store persistently. After a restart, the
client can send the prior LSN that it stored persistently as an
acknowledgement, but we need to ignore such an LSN to avoid retreating
confirm_flush LSN.
Diagnosed-by: Zhijie Hou <houzj.fnst@fujitsu.com>
Author: shveta malik <shveta.malik@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Reviewed-by: Dilip Kumar <dilipbalaut@gmail.com>
Tested-by: Nisha Moond <nisha.moond412@gmail.com>
Backpatch-through: 13
Discussion: https://postgr.es/m/CAJpy0uDZ29P=BYB1JDWMCh-6wXaNqMwG1u1mB4=10Ly0x7HhwQ@mail.gmail.com
Discussion: https://postgr.es/m/OS0PR01MB57164AB5716AF2E477D53F6F9489A@OS0PR01MB5716.jpnprd01.prod.outlook.com
Diffstat (limited to 'src/backend/utils/adt')
0 files changed, 0 insertions, 0 deletions