Re: Invalidate the subscription worker in cases where a user loses their superuser status
| От | Peter Smith | 
|---|---|
| Тема | Re: Invalidate the subscription worker in cases where a user loses their superuser status | 
| Дата | |
| Msg-id | CAHut+Ps8aFyK3dizyaOJrQ8kwioG+LdqKfmOfAfG7y+naOJHTQ@mail.gmail.com обсуждение исходный текст | 
| Ответ на | Re: Invalidate the subscription worker in cases where a user loses their superuser status (vignesh C <vignesh21@gmail.com>) | 
| Ответы | Re: Invalidate the subscription worker in cases where a user loses their superuser status | 
| Список | pgsql-hackers | 
Some review comments for v5. ====== src/backend/catalog/pg_subscription.c 1. GetSubscription - comment + /* Get superuser for subscription owner */ + sub->ownersuperuser = superuser_arg(sub->owner); + The comment doesn't seem very good. SUGGESTION /* Is the subscription owner a superuser? */ ====== 2. General - consistency Below are the code fragments using the new Subscription field. AlterSubscription_refresh: must_use_password = !sub->ownersuperuser && sub->passwordrequired; AlterSubscription: walrcv_check_conninfo(stmt->conninfo, sub->passwordrequired && !sub->ownersuperuser); LogicalRepSyncTableStart: must_use_password = MySubscription->passwordrequired && !MySubscription->ownersuperuser; run_apply_worker: must_use_password = MySubscription->passwordrequired && !MySubscription->ownersuperuser; ~ It is not a difference caused by this patch, but since you are modifying these lines anyway, I felt it would be better if all the expressions were consistent. So, in AlterSubscription_refresh IMO it would be better like: BEFORE must_use_password = !sub->ownersuperuser && sub->passwordrequired; SUGGESTION must_use_password = sub->passwordrequired && !sub->ownersuperuser; ====== Other than those trivial things, v5 LGTM. ====== Kind Regards, Peter Smith. Fujitsu Australia
В списке pgsql-hackers по дате отправления: