From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Abbas Butt <abbas(dot)butt(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marc Linster <marc(dot)linster(at)enterprisedb(dot)com>, "A(dot) Hayee" <hayee(dot)bhatti(at)enterprisedb(dot)com>, Hope Jiang <hope(dot)jiang(at)enterprisedb(dot)com>, Priti Sarode <priti(dot)sarode(at)enterprisedb(dot)com>, Ahsan Hadi <ahsan(dot)hadi(at)enterprisedb(dot)com> |
Subject: | Re: Latches API on windows |
Date: | 2017-10-09 13:56:10 |
Message-ID: | 12956.1507557370@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Craig Ringer <craig(at)2ndquadrant(dot)com> writes:
> On 9 October 2017 at 21:26, Abbas Butt <abbas(dot)butt(at)enterprisedb(dot)com> wrote:
>> In my case this is not true, I am calling InitSharedLatch in _PG_init
>> which gets called at CREATE EXTENSION time.
>> My question : Is there a way to get the latches API work on windows
>> the way it is working on Linux?
> I suspect you'd need to do it by having your extension load via
> shared_preload_libraries, registering its latch in shmem_startup_hook
Yeah. That would also let you request your shared memory area honestly,
instead of relying on there being some slop in the initial allocation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Abbas Butt | 2017-10-09 13:59:38 | Re: Latches API on windows |
Previous Message | Craig Ringer | 2017-10-09 13:47:39 | Re: Latches API on windows |