Re: Chicken/egg problem with range types - Mailing list pgsql-general

From Tom Lane
Subject Re: Chicken/egg problem with range types
Date
Msg-id 23921.1342620947@sss.pgh.pa.us
Whole thread Raw
In response to Re: Chicken/egg problem with range types  (Alban Hertroys <haramrae@gmail.com>)
Responses Re: Chicken/egg problem with range types  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general
Alban Hertroys <haramrae@gmail.com> writes:
> On 18 Jul 2012, at 5:08, Tom Lane wrote:
>> I wonder whether we could improve this by postponing the no-shell-types
>> check from creation to function runtime.

> I don't suppose it'd be possible to treat it as a deferred constraint? Then the check would be moved to the end of
thetransaction. 

You mean, after we've already crashed, or allowed a security breach to
happen?  Doesn't sound very helpful.  In any case, my concern is that
there not be any added overhead, not about moving it around.

            regards, tom lane

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: installation problem with postgres password
Next
From: Craig Ringer
Date:
Subject: Re: installation problem with postgres password