Re: Facility for detecting insecure object naming

From: "Nasby, Jim" <nasbyj(at)amazon(dot)com>
To: Nico Williams <nico(at)cryptonector(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Noah Misch" <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Facility for detecting insecure object naming
Date: 2018-08-14 23:50:24
Message-ID: 2E44D611-4486-4CDC-A643-1408585DFAA9@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Aug 14, 2018, at 4:01 PM, Nico Williams <nico(at)cryptonector(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message 王翔宇 2018-08-15 02:04:20 Re: Get funcid when create function
Previous Message Thomas Munro 2018-08-14 23:32:28 Re: Postgres, fsync, and OSs (specifically linux)