Revert "Reject concurrent sequence refreshes". This reverts commit f38afa4abb04e85530c94b88daf11c089375daca.
That commit fixed a race that could leave stale sequence values on the subscriber after 'ALTER SUBSCRIPTION ... REFRESH SEQUENCES'. It did so by raising an ERROR during 'ALTER SUBSCRIPTION ... REFRESH SEQUENCES' whenever a sequence synchronization worker was already running for the subscription. That approach caused intermittent buildfarm failures, because the existing tests did not ensure the sequencesync worker had stopped before executing 'ALTER SUBSCRIPTION ... REFRESH SEQUENCES'. While discussing how to fix the tests, we concluded that blocking the command while a sequencesync worker is running is inconvenient for users. So we will fix the original race differently in a follow-up commit. Reported-by: Tom Lane <[email protected]> Author: Amit Kapila <[email protected]> Backpatch-through: 19 Discussion: https://postgr.es/m/[email protected] Discussion: https://postgr.es/m/[email protected] Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/fd27c7e64fe0d5d514ee5fa97250327ce33756fa Modified Files -------------- src/backend/commands/subscriptioncmds.c | 27 --------------------------- src/test/subscription/t/036_sequences.pl | 4 ---- 2 files changed, 31 deletions(-)
