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

Re: Paths for C functions (was Re: Re: backend dies on 7.1.1 loading large datamodel.)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Hentosh <hentosh(at)io(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Paths for C functions (was Re: Re: backend dies on 7.1.1 loading large datamodel.)
Date: 2001-05-10 18:32:54
Message-ID: Pine.LNX.4.30.0105091805460.757-100000@peter.localdomain (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Tom Lane writes:

> For obvious security reasons, the library path must only be settable by
> the dbadmin, and I see no good reason that it should be changeable
> on-the-fly.  But we could treat it as a postmaster-start-only GUC
> parameter...

On the fly could be useful for trying alternative sets of modules.  Also,
you could include such a SET command into your function loading script.

-- 
Peter Eisentraut   peter_e(at)gmx(dot)net   http://funkturm.homeip.net/~peter


In response to

pgsql-hackers by date

Next:From: Mark HollomonDate: 2001-05-10 19:26:07
Subject: Re: Re: PL/Python build
Previous:From: Joel BurtonDate: 2001-05-10 18:29:59
Subject: Re: Re: PL/Python build

pgsql-bugs by date

Next:From: Eric PareDate: 2001-05-10 19:25:03
Subject: order by using functions under unions
Previous:From: AlbertDate: 2001-05-10 15:06:30
Subject: Bug in plpgsql with execute ...

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