| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: create table like including storage parameter |
| Date: | 2025-12-17 06:41:06 |
| Message-ID: | CACJufxF=k+4Lcx=XTcZUfTAUOgq66sDXO=s_vkEFPt7s2LxaCA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
current, v7 the DOC changes:
+ <varlistentry id="sql-createtable-parms-like-opt-storage-paramter">
+ <term><literal>INCLUDING PARAMETERS</literal></term>
+ <listitem>
+ <para>
+ All table parameters, such as the <literal>storage
parameter</literal>
+ settings of the source table, will be copied. For table storage
+ parameters, see <xref linkend="sql-createtable-storage-parameters"/>
+ below for more information.
+ </para>
+ </listitem>
+ </varlistentry>
https://www.postgresql.org/docs/current/sql-altertable.html#SQL-ALTERTABLE-DESC-SET-ATTRIBUTE-OPTION
Does the "parameter" (INCLUDING PARAMETERS) definition is close to "option"?
This raises the question of whether we should also copy column-level options to
the new table.
What do you think?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rahila Syed | 2025-12-17 06:57:46 | Re: Segmentation fault on proc exit after dshash_find_or_insert |
| Previous Message | Kirill Reshke | 2025-12-17 06:40:37 | Re: Support named (destination) portals in extended proto for psql meta commands. |