From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | korryd(at)enterprisedb(dot)com |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: shared_preload_libraries support on Win32? |
Date: | 2007-01-29 19:39:34 |
Message-ID: | 20070129193934.GD14134@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
korryd(at)enterprisedb(dot)com wrote:
> > > And, shared_preload_libraries is processed (in the postmaster) before
> > > the shared-memory segment is created, so a shared_preload_library can
> > > call RequestAddinShmemSpace() and RequestAddinLWLocks(), but a
> > > local_preload_library cannot.
> >
> > That doesn't seem like an issue though, since the copy in the postmaster
> > will have done that anyway.
>
>
> You're right - we need the copy in the postmaster (to setup shared
> memory and LW locks), and we need 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() seems to fix
> the problem for me.
Just make sure you don't load the libraries in bgwriter et al ...
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | korryd | 2007-01-29 19:48:48 | Re: shared_preload_libraries support on Win32? |
Previous Message | Alvaro Herrera | 2007-01-29 19:32:42 | Re: [pgsql-patches] Autovacuum launcher patch |