Re: [INTERFACES] The persistance of C functions - Mailing list pgsql-interfaces

From Karel Zak - Zakkr
Subject Re: [INTERFACES] The persistance of C functions
Date
Msg-id Pine.LNX.3.96.1000210103409.21359B-100000@ara.zf.jcu.cz
Whole thread Raw
In response to The persistance of C functions  ("Bryan White" <bryan@arcamax.com>)
Responses Re: [INTERFACES] The persistance of C functions  ("Ross J. Reedstrom" <reedstrm@wallace.ece.rice.edu>)
List pgsql-interfaces
On Wed, 9 Feb 2000, Bryan White wrote:

> If I use CREATE FUNCTION for a C function in a .so file and then use the
> function and then change and recompile the function, what steps are needed
> to see the change?
> 
> As I see it the options are:
> A: do nothing, the function is reloaded on every invocation.
> B: Reopen the connection to the backend
> C: Restart the postmaster
> 
> I suspect B is correct but I would like to hear someone confirm it.

'B' is right - the postgreSQL not has any persisten cache for this, and 
if you restart connection a backend reload this information again.

Or you can drop/(re)create a function, it is total safe solution.
                        Karel



pgsql-interfaces by date:

Previous
From: Rini Dutta
Date:
Subject: how to make libpq on winnt using the 'win32.mak's
Next
From: "Alex Verstak"
Date:
Subject: Re: [INTERFACES] JDBC primary keys