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

From Nasby, Jim
Subject Re: Facility for detecting insecure object naming
Date
Msg-id 2E44D611-4486-4CDC-A643-1408585DFAA9@amazon.com
Whole thread Raw
In response to Re: Facility for detecting insecure object naming  (Nico Williams <nico@cryptonector.com>)
Responses Re: Facility for detecting insecure object naming
List pgsql-hackers
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.


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Postgres, fsync, and OSs (specifically linux)
Next
From: 王翔宇
Date:
Subject: Re: Get funcid when create function