From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 07:06:47 |
Message-ID: | 692FA3C9-20BA-4DD3-8601-3B2E2F1F46C5@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 18 Jul 2012, at 5:08, Tom Lane wrote:
> Scott Bailey <artacus72(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | KOTa | 2012-07-18 08:27:44 | Re: installation problem with postgres password |
Previous Message | Thomas Munro | 2012-07-18 06:25:52 | Re: index update |