On 20/04/17 14:41, Michael Paquier wrote: > On Thu, Apr 20, 2017 at 8:47 PM, Petr Jelinek > <petr.jeli...@2ndquadrant.com> wrote: >> Or you can drop the slot manually on upstream. > > Sure, but the point here is that if for example users have > client_min_messages set at least at warning, they may have no idea > that an underlying slot has been created. This is a confusing > experience for users. > > As subscription is a self-contained concept, it seems to me that any > errors happening should at least try to do some cleanup action before > just giving up processing, that would be a less frustrating > experience. >
Hmm well since this only affects the synchronization of table states/names, I guess we could just simply do that before we create the slot as there is no expectancy of consistency between slot and the table list snapshot. Any other potential errors will be out of control of CreateSubscription anyway. Thoughts? -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
