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 CAGRkXqTdNx_YBfNx0ZJ0f-osLHR+Z6-m9Ltm11mp0LDFmQ2tWw@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 Sawada-san,

I agree with you on both A and B, and I would keep the current approach.

For A, a parallel worker gets its roleId in InitializeSessionUserId(),
so any reset has to come after that and the window stays. It also would
not cover the bgworker case.

I did not try B. I share your concern that it changes how DROP DATABASE
FORCE treats parallel workers today, which I would not want in a
backpatch.

Thanks,
Shihao

pgsql-hackers by date:

Previous
From: Baji Shaik
Date:
Subject: Re: [PATCH] Unify duplicate-option handling across utility commands
Next
From: Ayoub Kazar
Date:
Subject: Re: [PROPOSAL] Expand OR clauses in joins to UNION ALL paths