On Tue, Oct 01, 2019 at 01:52:46PM +0900, Michael Paquier wrote: > This indicates that it is possible to reach GetCurrentCommandId() for > a parallel worker in this context. It is possible to get rid of the > problem by enforcing the following in the tests so as we have no > parallel plans: > SET max_parallel_workers = 0; > SET max_parallel_workers_per_gather = 0; > Or just use SetConfigOption as per the attached which would be a bit > cleaner, and both could be used as a temporary solution to cool down > the buildfarm but that does not feel completely right to me in the > long term. > > Any thoughts?
Actually, it makes little sense to allow parallel workers to log their activity in the module. So if there are no objections, I would like to fix that by checking after IsParallelWorker() in the hooks of the module. -- Michael
signature.asc
Description: PGP signature
