| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Georgios <gkokolatos(at)protonmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Relation wide 'LIKE' clause |
| Date: | 2020-06-10 10:08:23 |
| Message-ID: | bbfeb1aa-d8a9-360b-c26c-7ad8fbbb499d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-06-10 11:42, Georgios wrote:
> Postgres create table statement supports `LIKE source_table [like_option... ]`
> to specify `a table from which the new table automatically copies all column
> names, their data types, and their not-null constraints.` according to
> documentation [1].
>
> I am wondering if a similar clause would make sense to copy relation wide
> settings. For example consider a relation created like this:
>
> `CREATE TABLE source_table ([column, ...]) USING customam WITH (storage_parameter1 = value1, ... )`
We already have LIKE INCLUDING STORAGE. Maybe that should just be
updated to work like what you are asking for.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Georgios | 2020-06-10 10:17:44 | Re: Relation wide 'LIKE' clause |
| Previous Message | Amit Khandekar | 2020-06-10 09:52:25 | Re: calling procedures is slow and consumes extra much memory against calling function |