Re: Chicken/egg problem with range types

On 07/17/2012 08:08 PM, Tom Lane wrote:
> 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.
>
> This would limit what checking could be performed on the function body
> at creation time, but surely no worse than, say, a reference to a
> nonexistent table, which we allow.

How about using ALTER TYPE to set it after both the function and the
type have been created?

Scott