Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] Shared Objects (Dynamic loading)

From: "Jasbinder Bali" <jsbali(at)gmail(dot)com>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [GENERAL] Shared Objects (Dynamic loading)
Date: 2006-08-28 15:52:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-novice
Is there any way to check what all shared objects are loaded in the memory?
Also, when i say LOAD 'parser' where is the shared object i've
loaded dynamically
using CREATE FUNCTION, its says

ERROR:  could not access file "parser": No such file or directory

Why would it give me this error?

Thanks and regards,

On 8/24/06, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
> On Thu, Aug 24, 2006 at 03:29:55AM -0400, Jasbinder Bali wrote:
> > Also, when i dynamically load  a shared library and then later on change
> the
> > code, create the same shared library (same name) and run my function
> where
> > in the shared library is loaded, it takes the reference of the old
> shared
> > library.
> > why does this happen and how to get rid of this.
> The "C-Language Functions" documentation explains:
> "After it is used for the first time, a dynamically loaded object
> file is retained in memory.  Future calls in the same session to
> the function(s) in that file will only incur the small overhead of
> a symbol table lookup.  If you need to force a reload of an object
> file, for example after recompiling it, use the LOAD command or
> begin a fresh session."
> --
> Michael Fuhr

In response to


pgsql-novice by date

Next:From: Tom LaneDate: 2006-08-28 16:45:06
Subject: Re: [GENERAL] Shared Objects (Dynamic loading)
Previous:From: Julian HagenauerDate: 2006-08-28 14:50:13
Subject: Re: JAVA_OBJECT: Unkown type

pgsql-general by date

Next:From: Jorge GodoyDate: 2006-08-28 16:37:59
Subject: Re: Perl language creation failed
Previous:From: Silvela, Jaime (Exchange)Date: 2006-08-28 15:35:04
Subject: Re: speeding up big query lookup

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group