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

From Tom Lane
Subject Re: fix bgworkers in EXEC_BACKEND
Date
Msg-id 29347.1356674981@sss.pgh.pa.us
Whole thread Raw
In response to Re: fix bgworkers in EXEC_BACKEND  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2012-12-27 18:44:57 -0500, Tom Lane wrote:
>> 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.

> Well, the problem is, a shared library can't do that
> afaics. abc.num_workers would be using custom_variable_classes (well,
> whatever its called now, that it doesn't need to be configured).

We fixed that a few years ago, no?

http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=4605d1c98

If that's broken, we certainly need to fix it again.  This issue exists
for any parameter that feeds into shared memory sizing, which is exactly
why we changed it back then.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Next
From: Peter Eisentraut
Date:
Subject: SPI API and exceptions