| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Nico Williams <nico(at)cryptonector(dot)com> |
| Cc: | "Nasby, Jim" <nasbyj(at)amazon(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Facility for detecting insecure object naming |
| Date: | 2018-08-16 05:56:16 |
| Message-ID: | 20180816055616.GB3626005@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 15, 2018 at 10:40:55AM -0500, Nico Williams wrote:
> On Tue, Aug 14, 2018 at 11:50:24PM +0000, Nasby, Jim wrote:
> > 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.
>
> It would only require recomputing the bindings at relocation time. IMO
> PG should not allow extension relocation after installation either, but
> sadly it does.
Agreed. I wouldn't mind deprecating relocatable=true, if it helps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-08-16 06:22:25 | Re: Index Skip Scan |
| Previous Message | Andrew Gierth | 2018-08-16 05:55:10 | Re: Fix quadratic performance of regexp match/split functions |