Re: [16+] subscription can end up in inconsistent state
От | Jeff Davis |
---|---|
Тема | Re: [16+] subscription can end up in inconsistent state |
Дата | |
Msg-id | 5dff4caf26f45ce224a33a5e18e110b93a351b2f.camel@j-davis.com обсуждение исходный текст |
Ответ на | Re: [16+] subscription can end up in inconsistent state (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: [16+] subscription can end up in inconsistent state
Re: [16+] subscription can end up in inconsistent state Re: [16+] subscription can end up in inconsistent state |
Список | pgsql-bugs |
On Mon, 2023-09-11 at 08:59 +0530, Amit Kapila wrote: > Can we think of calling walrcv_check_conninfo() when the following > check is true (MySubscription->passwordrequired && > !superuser_arg(MySubscription->owner))? IIUC this has to be done for > both apply_worker and tablesync_worker. To me, it would make sense to just have walrcv_connect() do both checks (a) and (b) -- rather than only check (b) -- when must_use_password is true. Separating these checks (which are really two parts of the same check) led to this problem in the first place. Another thought: we may also need to invalidate the subscription worker in cases where a user loses their superuser status. Regards, Jeff Davis
В списке pgsql-bugs по дате отправления: