From: Jon Horsman <horshaq@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: sql pgsql <pgsql-sql@postgresql.org>
Subject: Re: When is a shared library unloaded?
Date: Wed, 15 Aug 2007 09:16:23 -0400
Message-ID: <4f4c2a010708150616se51de62u3c59d7722c3d5097@mail.gmail.com> (raw)
In-Reply-To: <10738.1187120065@sss.pgh.pa.us>
References: <4f4c2a010708141142p70c199ednab3ceffb4ce9f138@mail.gmail.com>
<10738.1187120065@sss.pgh.pa.us>
> "Jon Horsman" <horshaq@gmail.com> writes:
> > I'm randomly having issues with my triggers not firing (it turns out
> > they are getting removed) and when i turned INFO logs on i saw the
> > following
>
> > 2007-08-14 13:41:44.740305500 LOCATION: _fini, medbevent_init.c:129
> > 2007-08-14 13:41:45.790850500 INFO: 00000: medbeventlib -Unloading
> > library _fini() is called
>
> > Could someone please explain when a shared library gets
> > loaded/unloaded and how this all works?
>
> Are you sure the above doesn't just occur during server process
> termination? AFAIK Postgres never unloads a library, except when you
> specifically command it to load an updated version via the LOAD command.
>
> regards, tom lane
Yup, the server process is still up and going, i have other clients
connected to postgres that still function when this happens. I'm not
using the LOAD command anywhere so thats not the problem. One of my
colleagues was doing some reading and said he found something that
stating that the fini() function is "unreliable", i'm not sure where
he read that though...
Jon.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: horshaq@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: When is a shared library unloaded?
In-Reply-To: <4f4c2a010708150616se51de62u3c59d7722c3d5097@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox