Re: fix bgworkers in EXEC_BACKEND - Mailing list pgsql-hackers

From Tom Lane
Subject Re: fix bgworkers in EXEC_BACKEND
Date
Msg-id 22625.1356651897@sss.pgh.pa.us
Whole thread Raw
In response to Re: fix bgworkers in EXEC_BACKEND  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: fix bgworkers in EXEC_BACKEND
Re: fix bgworkers in EXEC_BACKEND
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> I am still worried about the following scenario in the EXEC_BACKEND case:

> 1) postmaster starts
> 2) reads config
> 3) executes _PG_init for shared_preload_libraries
> 4) library 'abc' gets config value 'abc.num_workers = 2' and registers as many workers
> 5) some time goes by, workers, backends start
> 6) abc.num_workers gets changed to 3, SIGHUP

This is broken whether it's EXEC_BACKEND or not: you don't get to change
anything that determines the number of workers post-startup.
num_workers should have been declared PGC_POSTMASTER.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: fix bgworkers in EXEC_BACKEND
Next
From: Andres Freund
Date:
Subject: Re: fix bgworkers in EXEC_BACKEND