Re: Chicken/egg problem with range types

On 18 Jul 2012, at 5:08, Tom Lane wrote:

> Scott Bailey <artacus72@gmail.com> writes:
>> I'm trying to create a discrete range type and I'm having trouble with
>> the canonical function.

> I wonder whether we could improve this by postponing the no-shell-types
> check from creation to function runtime.  It would be annoying to have
> to make an additional catalog lookup at runtime just for typisdefined,
> but I think that probably we could fold it in with an existing fetch of
> the pg_type row during parsing of the calling query, so that no run-time
> overhead is added.


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.

Alban Hertroys

--
Screwing up is an excellent way to attach something to the ceiling.