Dear Bertrand, > Yeah, but I think they would produce "tuple concurrently updated" error (due > to > CatalogTupleUpdate) so that invalid information could not be used.
I confirmed with PG14 that tuple concurrently updated ERROR can be raised when ALTER SUBSCRIPTION DISABLE happens concurrently: ``` postgres=# ALTER SUBSCRIPTION sub DISABLE ; ERROR: tuple concurrently updated ``` It might be harmless but I think the correct ERROR should be reported: the patch should be backpatched. Thought? Best regards, Hayato Kuroda FUJITSU LIMITED
