| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(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-06 01:00:12 |
| Message-ID: | CAGRkXqS2RyJcFszRquot+b2m8UPM_xd-4QTrLuM257=v1SRhmw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Masahiko,
Attached v4 takes the partition lock and rechecks the leader, as you
suggested. The databaseId test is gone, since the recheck makes it
redundant. The new test and the role matrix give the same results as
v2.
I did not add the !OidIsValid(leader->roleId) check. DROP DATABASE
fails on the REPACK slot first anyway.
Thanks,
shihao zhong
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Fix-DROP-DATABASE-FORCE-to-terminate-parallel-wor.patch | application/octet-stream | 7.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-10-06 01:04:37 | Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names |
| Previous Message | shihao zhong | 2026-10-06 00:43:07 | Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF |