Closed marco44 closed 3 years ago
Thanks for the report! Indeed, parallel worker explicitly set all non default GUCs to ensure that they will have the same environment as the leader process. This can be also happen with any DML query using parallelism.
I think that simply ignoring parallel workers for that message should be enough, as the goal is to warn DBA that even though the new value is accepted, it won't enforce it immediately, so it can't be use as an immediate way to release dynamic shared memory. This is done in https://github.com/rjuju/pg_shared_plans/commit/99e054a962d7ce5bef90e3557b20492315cc4cea.
Problem solved
Great!
The whole message in the log is this: