Fix concurrent sequence drops during sequence synchronization. A recent BF failure showed that commit 7a485bd641 did not handle the case where a sequence is dropped concurrently during sequence synchronization on the subscriber. Previously, pg_get_sequence_data() would ERROR out if the sequence was dropped concurrently. After 7a485bd641, it instead returns NULL, which leads to an assertion failure on the subscriber.
To handle this change, update sequence synchronization to skip sequences for which pg_get_sequence_data() returns NULL. Author: vignesh C <[email protected]> Reviewed-by: Hayato Kuroda <[email protected]> Reviewed-by: Amit Kapila <[email protected]> Discussion: https://postgr.es/m/CALDaNm0FoGdt+1mzua0t-=wYdup5_zmFrvfNf-L=mgbnj9h...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/1ba3eee89a7534a895187f6484f2f5e04f9c3c62 Modified Files -------------- src/backend/replication/logical/sequencesync.c | 33 +++++++++++++++++++------- 1 file changed, 25 insertions(+), 8 deletions(-)
