Re: Chicken/egg problem with range types

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alban Hertroys <haramrae(at)gmail(dot)com>
Cc: Scott Bailey <artacus72(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Chicken/egg problem with range types
Date: 2012-07-18 14:15:47
Message-ID: 23921.1342620947@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alban Hertroys <haramrae(at)gmail(dot)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 the transaction.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message KOTa 2012-07-18 14:37:54 Re: installation problem with postgres password
Previous Message Alban Hertroys 2012-07-18 14:13:41 Re: installation problem with postgres password