On Thu, Aug 25, 2022 at 8:17 PM Jelte Fennema <jelte.fenn...@microsoft.com> wrote: > > Without this patch concurrent ALTER/DROP SUBSCRIPTION statements for > the same subscription could result in one of these statements returning the > following error: > > ERROR: XX000: tuple concurrently updated > > This patch fixes that by re-fetching the tuple after acquiring the lock on the > subscription. The included isolation test fails most of its permutations > without this patch, with the error shown above. >
Won't the same thing can happen for similar publication commands? Why is this unique to the subscription and not other Alter/Drop commands? -- With Regards, Amit Kapila.
