Re: Can a background worker exist without shared memory access for EXEC_BACKEND cases? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Can a background worker exist without shared memory access for EXEC_BACKEND cases?
Date
Msg-id CA+TgmoaxRVjcXq+-Bx24WPJQPBSgHO_sedMEP-ie-C9K4mnGtA@mail.gmail.com
Whole thread Raw
In response to Re: Can a background worker exist without shared memory access for EXEC_BACKEND cases?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Can a background worker exist without shared memory access for EXEC_BACKEND cases?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Tue, Aug 4, 2020 at 7:27 AM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
> I could get these points earlier in my initial analysis. In fact, I
> could figure out the flow on Windows, how these parameters are shared
> using a shared file(CreateFileMapping(), MapViewOfFile()), and the
> shared file name being passed as an argv[2] to the child process, and
> the way child process uses this file name to read the backend
> parameters in read_backend_variables().

Doesn't that happen even if the background worker isn't declared to
use BGWORKER_SHMEM_ACCESS? See StartBackgroundWorker(): IIUC, we start
with shared memory access, then afterwards detach.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: new heapcheck contrib module
Next
From: Robert Haas
Date:
Subject: Re: Confusing behavior of create table like