Re: Facility for detecting insecure object naming

From: Chapman Flack <chap(at)anastigmatix(dot)net>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Facility for detecting insecure object naming
Date: 2018-08-14 23:17:20
Message-ID: 6ad8aa29-5d60-222e-f912-b8f10a20c12c@anastigmatix.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/14/2018 07:01 PM, Nico Williams 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.

What would the interface to that look like for out-of-tree PL
maintainers?

-Chap

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-08-14 23:28:49 C99 compliance for src/port/snprintf.c
Previous Message Edmund Horner 2018-08-14 23:11:54 Re: Tid scan improvements