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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
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-08 16:21:52
Message-ID: 29941.989338912@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> where the backend automatically assumes that a relative path is relative
>> to $PGLIB. I'd like to see the backend adding the file extension too,
>> to avoid platform dependencies (".so" is not universal).

> We could have a run-time parameter that sets a path where to look for
> modules.

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...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2001-05-08 18:22:07 Re: [BUGS] Doc bug undefined special characters
Previous Message Peter Eisentraut 2001-05-08 16:07:27 Re: Paths for C functions (was Re: Re: backend dies on 7.1.1 loading large datamodel.)

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-05-08 16:28:08 Re: Is `#!/bin/sh' configurable?
Previous Message Doug McNaught 2001-05-08 16:14:03 Re: Is `#!/bin/sh' configurable?