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

Re: Permissions checks for range-type support functions

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Permissions checks for range-type support functions
Date: 2011-11-23 14:01:50
Message-ID: CA+TgmoaXcR3xFYcGus6Wz-CEO-Q2K9j4N6T-eBu4TPocJKH7Pw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-11-23 14:25:10
Subject: Re: Not HOT enough
Previous:From: Robert HaasDate: 2011-11-23 14:00:12
Subject: Re: Not HOT enough

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