Re: WIP: generalized index constraints - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: WIP: generalized index constraints
Date
Msg-id 37ed240d0908201814k66c3b493n198b7b07c7738799@mail.gmail.com
Whole thread Raw
In response to Re: WIP: generalized index constraints  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: WIP: generalized index constraints  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
2009/8/21 Heikki Linnakangas <heikki.linnakangas@enterprisedb.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


pgsql-hackers by date:

Previous
From: Mischa Sandberg
Date:
Subject: Re: Multi-pass planner
Next
From: Jeff Davis
Date:
Subject: Re: WIP: generalized index constraints