Re: Regarding BGworkers - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Regarding BGworkers
Date
Msg-id CA+TgmoaGgYGm=VepraJD5MmSEuaO=dYp=HWVhhqChMvX5_N9zQ@mail.gmail.com
Whole thread Raw
In response to Regarding BGworkers  (Amit kapila <amit.kapila@huawei.com>)
Responses Re: Regarding BGworkers  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Sun, Jul 28, 2013 at 1:26 AM, Amit kapila <amit.kapila@huawei.com> wrote:
> 1. Bgworker.c -
>                 FindRegisteredWorkerBySlotNumber()
>         {
>           ..
>           /*
>      * Copy contents of worker list into shared memory.  Record the
>      * shared memory slot assigned to each worker.  This ensures
>      * a 1-to-1 correspondence betwen the postmaster's private list and
>      * the array in shared memory.
>      */
>                   ..
>                  }
>      a. Comment in function doesn't seem to be appropriate. It seems copy-pasted from function
>         BackgroundWorkerShmemInit
>      b. all function's except this have function header to explain a bit about function, though
>         it might not be required here, but not sure so pointed.

Fixed.

> 2. Shouldn't function
> do_start_bgworker()/StartOneBackgroundWorker(void) be moved to bgworker.c
>    as similar functions AutoVacWorkerMain()/PgArchiverMain() are in their respective files.

Yes, perhaps so.  Other votes?

> 3. bgworker.h - file header still contains explanation only as per old functionality.
>                 Not sure, if it needs to be updated for new functionality of dynamic workers.

Fixed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: pg_basebackup vs. Windows and tablespaces
Next
From: Robert Haas
Date:
Subject: Re: replication_reserved_connections