<blockquote type="CITE"><pre>
<font color="#000000">>> You're right - we need the copy in the postmaster (to setup shared</font>
<font color="#000000">>> memory and LW locks), and we need them in the backends too.</font>
<font color="#000000">> Just make sure you don't load the libraries in bgwriter et al ...</font>
<font color="#000000">I see that Korry's patch doesn't do that, but I'm wondering why exactly.</font>
<font color="#000000">In a Unix environment such libraries *would* be propagated into bgwriter</font>
<font color="#000000">and every other postmaster child; is there a reason for the setup on</font>
<font color="#000000">Windows to be different? In particular, what about autovacuum, which</font>
<font color="#000000">ISTM should be as close to a standard backend as possible?</font>
</pre></blockquote> I thought about that too... does autovacuum ever need to re-index? If so, it seems that it would
needaccess to any index functions (for function-based indexes) that might reside in a shared_preload_library.<br /><br
/><blockquotetype="CITE"><pre>
<font color="#000000">Either way we do it, authors of plugins used this way will have to test</font>
<font color="#000000">both cases (I'm glad I insisted on EXEC_BACKEND mode being testable under</font>
<font color="#000000">Unix ...)</font>
</pre></blockquote><br /> And I'm glad that RequestAddinShmemSpace() and RequestAddinLWLocks() don't complain if called
afterpostmaster start :-)<br /><br /> -- Korry<br /><table cellpadding="0" cellspacing="0"
width="100%"><tr><td><br/><br /> --<br /> Korry Douglas <a
href="mailto:korryd@enterprisedb.com">korryd@enterprisedb.com</a><br/> EnterpriseDB <a
href="http://www.enterprisedb.com">http://www.enterprisedb.com</a></td></tr></table>
