On Wed, Jul 12, 2006 at 06:47:56PM -0700, Marc Munro wrote:
> On a related note, I can see no way to release Veil's shared memory
> segment when postgres is shut down. Perhaps I should be thinking about
> making the management of such shared memory segments something that
> postgres does on behal
Marc Munro <[EMAIL PROTECTED]> writes:
> ... A better solution from my point of view would be
> to simply move the call to process_preload_libraries to a point after
> shared memory has been set up. Is there some reason this could not be
> done?
That would make it impossible for a preloaded libr
On Wed, 2006-07-12 at 02:18 -0300, I wrote:
> I am trying to create an initialisation function that is called using
> the preload_libraries option.
>
> The purpose of this is to set up shared memory for Veil, independant
> of postgres' own shared memory. Simple init functions work fine, but
> as
I am trying to create an initialisation function that is called using
the preload_libraries option.
The purpose of this is to set up shared memory for Veil, independant of
postgres' own shared memory. Simple init functions work fine, but as
soon as I place calls to ShemAlloc, or LWLockAssign, th
