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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-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

Browse pgsql-bugs by date

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Hollomon 2001-05-10 19:26:07 Re: Re: PL/Python build
Previous Message Joel Burton 2001-05-10 18:29:59 Re: Re: PL/Python build