Request a Demo
Home   >   mailing lists

Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers - Mailing list pgsql-hackers

From shihao zhong
Subject Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
Date
Msg-id CAGRkXqS2RyJcFszRquot+b2m8UPM_xd-4QTrLuM257=v1SRhmw@mail.gmail.com
Whole thread
In response to Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Tree view
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

pgsql-hackers by date:

Previous
From: shihao zhong
Date:
Subject: Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF
Next
From: shihao zhong
Date:
Subject: Re: [PG19] COPY (query) TO ... (FORMAT json) uses the table's column names