| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers |
| Date: | 2026-10-15 21:14:26 |
| Message-ID: | CAD21AoDMqAnRMaVM6kKC9TF7aNROJvJAKWx3P5WGTA5R2Khj8g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 14, 2026 at 7:14 PM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> Hi,
>
> On Wed, Oct 14, 2026 at 12:03 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> >
> > I think that distinction is not visible to users. A parallel worker
> > always connects to the same database as its leader, so the leader is
> > checked too, with the same role.
>
> Since the code comments already specify that, I think it is fine not
> to have anything in the docs. So I removed the doc changes and
> addressed the other comments as well. Please find the attached v4
> patches.
Thank you for updating the patch! I've pushed the patch with some
minor adjustments.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-10-15 21:21:03 | Re: [PATCH] Doc fix for autovacuum_max_parallel_workers |
| Previous Message | Baji Shaik | 2026-10-15 21:01:05 | Re: [PATCH] Doc fix for autovacuum_max_parallel_workers |