From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: ADD/DROP INHERITS |
Date: | 2006-06-10 16:23:06 |
Message-ID: | 597.1149956586@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> I also haven't checked the constraint name. To do so it would make sense to
> use a small hash table.
No, it'd make sense to use strcmp(). It's unlikely that there will be
enough constraints attached to any one table to justify use of any but
the simplest algorithm. AFAICS you should just iterate through the
child constraints looking for matches ... and I'd suggest checking the
name first, as that will save a whole lot more work in reverse-compiling
than any amount of tenseness in the matching code.
> I'm ignoring unique, primary key, and foreign key constraints on the theory
> that these things don't really work on inherited tables yet
> anyways.
Yeah, the consistent thing to do with these is nothing, until something
is done about the generic problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-10 16:29:53 | Re: Ranges for well-ordered types |
Previous Message | Martijn van Oosterhout | 2006-06-10 16:11:02 | Re: How to avoid transaction ID wrap |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-06-10 16:43:17 | Re: ADD/DROP INHERITS |
Previous Message | Andrew Dunstan | 2006-06-10 14:16:15 | drop if exists remnainder (reprise) |