Skip site navigation (1) Skip section navigation (2)

Re: Permissions checks for range-type support functions

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Permissions checks for range-type support functions
Date: 2011-11-23 15:27:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Excerpts from Robert Haas's message of mié nov 23 11:01:50 -0300 2011:
> On Tue, Nov 22, 2011 at 6:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > 2. The ANALYZE option is flat out dangerous, because it allows any
> > function with the signature "f(internal) returns bool" to be called as
> > though it's a typanalyze function.  There are a couple of such functions
> > in the catalogs already, and either of them will probably crash the
> > backend if invoked as typanalyze on a range column.
> It's always seemed mildly insane to me that we don't distinguish
> between different flavors of "internal".  That seems like an accident
> waiting to happen.

Well, before we had INTERNAL, there was only OPAQUE which conflated even
more things that we now distinguish (at least trigger and cstring, not
sure if there were others).

Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2011-11-23 15:28:38
Subject: Re: Not HOT enough
Previous:From: Alvaro HerreraDate: 2011-11-23 15:20:44
Subject: Re: Not HOT enough

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group