Em sex., 27 de mar. de 2026 às 03:20, Masahiko Sawada <sawada.mshk@gmail.com> escreveu:
I've attached the updated patch. I believe I've addressed all comments I got so far. In addition to that, I've refactored is_table_publishable_in_publication() and added more regression tests.
Today I had to create a few more schemas and see that problem again, how the publisher is affected, almost crashing due to the overload.
That was because max_sync_workers_per_subscription was set to 10, which caused 10 simultaneous connections to call this function immediately after the refresh publication command.
Wouldn't it be good to document on this GUC that if your publisher server is running version <= 18 then is it advisable to set this GUC to a really low value ?
Because ok, version 19 is fine, will be covered, but all publisher servers that are not updated will continue to have this trouble.
The publisher will be severely penalized when the subscription refreshes its publication.
