| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Parallel heap vacuum |
| Date: | 2025-04-04 21:34:53 |
| Message-ID: | CAD21AoCnLa2y0LV39dPvYD4QYpRz-xqPJFCnjwzS7DhnvdSRZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 4, 2025 at 11:05 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> On Tue, Apr 1, 2025 at 5:30 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> >
> >
> > I've attached the new version patch. There are no major changes; I
> > fixed some typos, improved the comment, and removed duplicated codes.
> > Also, I've updated the commit messages.
>
> I haven't looked closely at this version but I did notice that you do
> not document that parallel vacuum disables eager scanning. Imagine you
> are a user who has set the eager freeze related table storage option
> (vacuum_max_eager_freeze_failure_rate) and you schedule a regular
> parallel vacuum. Now that table storage option does nothing.
Good point. That restriction should be mentioned in the documentation.
I'll update the patch.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-04-04 21:47:34 | Re: SQLFunctionCache and generic plans |
| Previous Message | Masahiko Sawada | 2025-04-04 21:32:24 | Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row |