Re: Facility for detecting insecure object naming - Mailing list pgsql-hackers

From Nico Williams
Subject Re: Facility for detecting insecure object naming
Date
Msg-id 20180815154054.GA29462@localhost
Whole thread Raw
In response to Re: Facility for detecting insecure object naming  ("Nasby, Jim" <nasbyj@amazon.com>)
Responses Re: Facility for detecting insecure object naming
List pgsql-hackers
On Tue, Aug 14, 2018 at 11:50:24PM +0000, Nasby, Jim wrote:
> On Aug 14, 2018, at 4:01 PM, Nico Williams <nico@cryptonector.com> wrote:
> > 
> > On Tue, Aug 14, 2018 at 03:00:55PM +0000, Robert Haas wrote:
> >> The more I think about it, the more I think having a way to set a
> >> lexically-scoped search path is probably the answer.  [...]
> > 
> > Yes please!
> > 
> > This is what I want.  Evaluate the search_path at function definition
> > time, and record code with fully-qualified symbols in the catalog.
> 
> Unfortunately, that falls apart for relocatable extensions.

It would only require recomputing the bindings at relocation time.  IMO
PG should not allow extension relocation after installation either, but
sadly it does.

Nico
-- 


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Facility for detecting insecure object naming
Next
From: Tom Lane
Date:
Subject: Re: C99 compliance for src/port/snprintf.c