From: | Brendan Jurd <direvus(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: generalized index constraints |
Date: | 2009-08-21 01:14:21 |
Message-ID: | 37ed240d0908201814k66c3b493n198b7b07c7738799@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/8/21 Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>:
> Jeff Davis wrote:
>> I'm leaning toward not allowing it at CREATE TABLE time.
>
> Seems reasonable to me too.
>
+1
There are plenty of other things to do with tables that you can't mix
directly into a CREATE TABLE statement (grant permissions, create
triggers, change owner, to name a few) so this would not be a surprise
-- or a hardship -- for users IMO.
As an aside, Jeff, have you considered how this feature would interact
with CREATE TABLE ... LIKE parent_table [ { INCLUDING | EXCLUDING } {
DEFAULTS | CONSTRAINTS | INDEXES } ] ... }? What if someone asks to
include indexes but not constraints? Vice-versa? Will these cases be
handled gracefully?
Cheers,
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2009-08-21 01:49:07 | Re: WIP: generalized index constraints |
Previous Message | Mischa Sandberg | 2009-08-20 22:11:16 | Re: Multi-pass planner |