From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | elein <elein(at)varlena(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inheritance, CREATE TABLE LIKE, and partitioned tables |
Date: | 2006-06-26 21:03:54 |
Message-ID: | 87y7vjwrwl.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
elein <elein(at)varlena(dot)com> writes:
> People will turn around and immediately as for create table like without us
> making the assumptions it wanted all of the extras that come with inheritance.
> COPY is a copy of the table, not additional functionality. The added flexibility
> of adding only what is necessary makes more sense than going in to guess
> what was added and removing it later if it is not needed.
>
> This does not preclude adding a copy table like (with extras) though if you must.
I'm not too sure what you're saying here. But just to be clear, the spec
specifies what CREATE TABLE LIKE does and does not copy. Any behaviour
different from the spec would have to be explicitly requested with an optional
clause.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-26 21:08:27 | Re: "Truncated" tuples for tuple hash tables |
Previous Message | Simon Riggs | 2006-06-26 20:59:07 | Re: "Truncated" tuples for tuple hash tables |