Is it a postgres shared object only? Then shuting down and restarting
postgres should have worked. If it is a OS shared object then my best guess
is postgres will see it already in memory and not reload the object/lib. In
which case you will need to bounce the OS. Is it possible another program
is also using that object? Then shuting that program down also and
restarting postgres may do the trick.
One thing though, if the OS or another program is also using that shared
object isn't there a risk to having a newer version being loaded by postgres
affect other things?
----- Original Message -----
From: "Kris Kiger" <kris@musicrebellion.com>
To: "Postgres Admin List" <pgsql-admin@postgresql.org>
Sent: Tuesday, December 09, 2003 10:35 AM
Subject: [ADMIN] Postgres grabbing an old shared object
> Is there a way to force a shared object to reload? I've compiled a new
> version of a .so, but postgres seems to be pulling the old version out
> of memory. I've tried deleting the .so and recompiling it, but postgres
> is insistant, for some reason, of using the old version. Any ideas?
> Thanks for the help
>
> Kris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
