Re: Facility for detecting insecure object naming

From: Nico Williams <nico(at)cryptonector(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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:01:14
Message-ID: 20180814230113.GF30604@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Nico
--

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Asim R P 2018-08-14 23:08:54 Re: Postgres, fsync, and OSs (specifically linux)
Previous Message Shawn Debnath 2018-08-14 21:35:00 Proposal: SLRU to Buffer Cache