| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BackendPidGetProc doesn't return PGPROC for background worker? |
| Date: | 2015-05-15 05:30:07 |
| Message-ID: | 5555845F.2020906@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-15 PM 02:13, Pavel Stehule wrote:
> 2015-05-15 3:39 GMT+02:00 Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>:
>> One reason for this may be that the worker was not started with the flag
>> BGWORKER_SHMEM_ACCESS which is necessary to perform InitProcess() that
>> would
>> initialize a PGPROC entry for it. But if you'd used the same method for
>> initializing workers as test_shm_mq_setup(), then it should have.
>>
>
> I have it
>
See my other (the last) email. You said you created a bgworker from bgworker,
so if the parent bgworker did not perform
BackgroundWorkerInitializeConnection, then it would not be found in ProcArray.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2015-05-15 05:32:19 | Re: upper planner path-ification |
| Previous Message | Pavel Stehule | 2015-05-15 05:18:03 | Re: proposal: contrib module - generic command scheduler |