| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, 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-05 03:35:01 |
| Message-ID: | CAGRkXqR-ayAKd9oJSxhhkyoP0avMb6kmHtRCD7DnxkGZJz_e2Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Bharath,
v2 looks right. The new test fails without your change
and passes with it. Attached v3 is only a rebase over head.
A superuser's parallel worker is still refused, other role cases
did not change.
The check also covers the REPACK decoding worker, which connects as
the table owner. DROP DATABASE fails on its slot first, so that looks
fine.
I did not test the bgworker case. The check does not look at the
backend type, and such a bgworker leaves roleId unset like autovacuum
does, so I think it works too.
Thanks,
Shihao
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Fix-DROP-DATABASE-FORCE-to-terminate-parallel-wor.patch | application/octet-stream | 7.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2026-10-05 03:35:35 | RE: Session in aborted transaction misses effective_wal_level change |
| Previous Message | Koshi Shibagaki (Fujitsu) | 2026-10-05 03:23:37 | [PATCH] pg_walsummary: suppress limit output with --quiet |