| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Denis Laxalde <denis(dot)laxalde(at)dalibo(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |
| Date: | 2021-08-26 13:43:34 |
| Message-ID: | CAOBaU_bhhOJwY_49aLbnd873aR7HR0j-A2b_Zgk4AHJSifuSLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le jeu. 26 août 2021 à 21:38, Daniel Gustafsson <daniel(at)yesql(dot)se> a écrit :
> > On 26 Aug 2021, at 15:09, Bruce Momjian <bruce(at)momjian(dot)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 extension forcing autovacuum to
be on for instance.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2021-08-26 13:59:49 | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |
| Previous Message | Bruce Momjian | 2021-08-26 13:42:29 | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |