| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Smith <smithpb2250(at)gmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Parallel heap vacuum |
| Date: | 2025-09-18 17:48:02 |
| Message-ID: | CAD21AoCW-YTRf2ToEnhSk2x8BAxmt2iUHbCBdGPTbQhLosR15w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 17, 2025 at 5:24 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
>
>
>
> On 9/18/25 01:18, Masahiko Sawada wrote:
> > For your information, while the implementation itself is relatively
> > straightforward, we're still facing one unresolved issue; the system
> > doesn't support reloading the configuration file during parallel mode,
> > but it is necessary for autovacuum to update vacuum cost delay
> > parameters[2].
> >
>
> Hmmm, that's annoying :-(
>
> If it happens only for max_stack_depth (when setting it based on
> environment) maybe we could simply skip that when in parallel mode? But
> it's ugly, and we probably will have the same issue for any other
> GUC_ALLOW_IN_PARALLEL option in a file ...
We have the same issue for all non-GUC_ALLOW_IN_PARALLEL parameters.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-09-18 18:15:37 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Robert Haas | 2025-09-18 17:38:44 | Re: PG 18 relnotes and RC1 |