Re: [PATCH] Disable bgworkers during servers start in pg_upgrade
От | Daniel Gustafsson |
---|---|
Тема | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |
Дата | |
Msg-id | 30D4153D-8F40-4BB8-838B-142D2C4EB4F0@yesql.se обсуждение исходный текст |
Ответ на | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade (Julien Rouhaud <rjuju123@gmail.com>) |
Ответы |
Re: [PATCH] Disable bgworkers during servers start in pg_upgrade
|
Список | pgsql-hackers |
> On 26 Aug 2021, at 15:43, Julien Rouhaud <rjuju123@gmail.com> wrote: > > Le jeu. 26 août 2021 à 21:38, Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> a écrit : > > On 26 Aug 2021, at 15:09, Bruce Momjian <bruce@momjian.us <mailto:bruce@momjian.us>> wrote: > > > Basically, pg_upgrade has avoided any backend changes that could be > > controlled by GUCs and I am not sure we want to start adding such > > changes for just this. > > In principle I think it’s sound to try to avoid backend changes where possible > without sacrificing robustness. > > I agree, but it seems quite more likely that an extension relying on a bgworker changes this guc, compared to an extensionforcing autovacuum to be on for instance. Agreed, in this particular case I think there is merit to the idea of enforcing it in the backend. -- Daniel Gustafsson https://vmware.com/
В списке pgsql-hackers по дате отправления: