| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: CREATE TABLE LIKE including all not including storage parameters? |
| Date: | 2017-09-05 10:26:34 |
| Message-ID: | CAB7nPqSpHbpJSoZ3mB=Bj_Jji+Hjgk1tiS69DFbZ=OY+HpuvwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Sep 5, 2017 at 6:45 PM, Achilleas Mantzios
<achill(at)matrix(dot)gatewaynet(dot)com> wrote:
> Am I doing something wrong here?
From the documentation:
https://www.postgresql.org/docs/devel/static/sql-createtable.html
STORAGE settings for the copied column definitions will be copied only
if INCLUDING STORAGE is specified. The default behavior is to exclude
STORAGE settings, resulting in the copied columns in the new table
having type-specific default settings. For more on STORAGE settings,
see Section 66.2.
And in this case storage parameters refer to column-specific settings,
not table-level storage parameters, which are defined here by toast:
https://www.postgresql.org/docs/devel/static/storage-toast.html
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2017-09-05 10:34:19 | Re: CREATE TABLE LIKE including all not including storage parameters? |
| Previous Message | Achilleas Mantzios | 2017-09-05 09:45:13 | Re: CREATE TABLE LIKE including all not including storage parameters? |