Re: shared_preload_libraries support on Win32? - Mailing list pgsql-hackers

From
Subject Re: shared_preload_libraries support on Win32?
Date
Msg-id 1170100128.8452.149.camel@sakai.localdomain
Whole thread Raw
In response to Re: shared_preload_libraries support on Win32?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: shared_preload_libraries support on Win32?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
<blockquote type="CITE"><pre>
<font color="#000000">> And, shared_preload_libraries is processed (in the postmaster) before</font>
<font color="#000000">> the shared-memory segment is created, so a shared_preload_library can</font>
<font color="#000000">> call RequestAddinShmemSpace() and RequestAddinLWLocks(), but a</font>
<font color="#000000">> local_preload_library cannot.</font>

<font color="#000000">That doesn't seem like an issue though, since the copy in the postmaster</font>
<font color="#000000">will have done that anyway.</font>
</pre></blockquote><br /> You're right - we need the copy in the postmaster (to setup shared memory and LW locks), and
weneed them in the backends too.  I just want to avoid having to set both shared_preload_libraries and
local_preload_libraries(to the same thing).  Adding a call to process_shared_preload_libraries() in SubPostmasterMain()
seemsto fix the problem for me.<br /><br /> Thanks for your input.  I'll submit a patch.<br /><br /><br />            
--Korry  

pgsql-hackers by date:

Previous
From: Markus Schiltknecht
Date:
Subject: Re: [pgsql-patches] Autovacuum launcher patch
Next
From: Alvaro Herrera
Date:
Subject: Re: [pgsql-patches] Autovacuum launcher patch