| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CREATE LIKE INCLUDING COMMENTS and STORAGES |
| Date: | 2009-09-13 09:33:36 |
| Message-ID: | 37ed240d0909130233p605613a4r182c049e0773ec80@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/9/9 Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>> This INCLUDING STORAGE is supposed to copy reloptions?
>
> No. It copies only storage parameters of columns to control TOAST policy.
> It might be good to have some features to copy reloptions with convenient
> way, but it will be done in another patch.
>
>> to me it sounds like it's copying the
>> underlying storage i.e. data, which would be very surprising. What
>> about "INCLUDING STORAGE OPTIONS"?
It *would* be very surprising. An option to include data would
probably be called "INCLUDING DATA" =)
>
> Hmm, but we have the following syntax already:
> ALTER TABLE table ALTER COLUMN column SET STORAGE ...
> Do you also think it should be "SET STORAGE OPTION ..." ?
>
Personally, I think INCLUDING STORAGE makes as much sense as you can
expect using just one word, and as Itagaki-san points out it
correlates well with the syntax for ALTER COLUMN.
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-09-13 13:42:44 | Re: [COMMITTERS] pgsql: Add Unicode support in PL/Python |
| Previous Message | Brendan Jurd | 2009-09-13 09:08:42 | Re: WIP: generalized index constraints |