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 CAGRkXqR-ayAKd9oJSxhhkyoP0avMb6kmHtRCD7DnxkGZJz_e2Q@mail.gmail.com
Whole thread
In response to Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
List pgsql-hackers
Tree view
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

pgsql-hackers by date:

Previous
From: "Koshi Shibagaki (Fujitsu)"
Date:
Subject: [PATCH] pg_walsummary: suppress limit output with --quiet
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Session in aborted transaction misses effective_wal_level change