diff options
| author | Amit Kapila <akapila@postgresql.org> | 2024-06-11 10:51:34 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2024-06-11 10:51:34 +0530 |
| commit | d1ffcc7fa3c54de8b2a677a3e503fc808c7b419c (patch) | |
| tree | 8b308d8cd75697af755fa311342a013b33d97c5e /src/backend/utils/adt/jsonpath_exec.c | |
| parent | 3470391e169ed46fa646ea39ade4b9b6898adb17 (diff) | |
| download | postgresql-d1ffcc7fa3c54de8b2a677a3e503fc808c7b419c.tar.gz postgresql-d1ffcc7fa3c54de8b2a677a3e503fc808c7b419c.zip | |
Fix an assert in CheckPointReplicationSlots().
Commit e0b2eed047 assumed that the confirmed_flush LSN can't go backward.
However, it is possible that confirmed_flush LSN can go backward
temporarily when the client acknowledges a prior value of flush location.
This can happen when the client (subscriber in this case) acknowledges an
LSN it doesn't have to do anything for (say for DDLs) and thus didn't
store persistently. After restart, the client sends the prior value of
flush LSN which it had stored persistently and the server updates the
confirmed_flush LSN with that value.
The fix is to remove the assumption and not allow the prior value of
confirmed_flush LSN to be flushed to the disk.
Author: Vignesh C
Reviewed-by: Amit Kapila, Shlok Kyal
Discussion: https://postgr.es/m/CALDaNm3hgow2+oEov5jBk4iYP5eQrUCF1yZtW7+dV3J__p4KLQ@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions