From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Proposal: CREATE/ALTER DOMAIN ... STORAGE/COMPRESSION = ... |
Date: | 2022-08-20 07:47:15 |
Message-ID: | 9bda7e17-70f8-99a7-f1d5-a799311899da@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 17.08.22 11:43, Aleksander Alekseev wrote:
> Do you think it will be useful to specify STORAGE and/or COMPRESSION
> for domains?
Domains are supposed to a logical construct that restricts the accepted
values for a data type (it's in the name "domain"). Expanding that into
a general "column definition macro" seems outside its scope. For
example, what would be the semantics of this when such a domain is a
function argument or return value?
> As an example, this will allow creating an alias for TEXT with
> EXTERNAL storage strategy. In other words, to do the same we do with
> ALTER TABLE, but for types. This feature is arguably not something
> most people are going to use, but it shouldn't be difficult to
> implement and/or maintain either.
Considering how difficult it has been to maintain domains in just their
current form, I don't believe that.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-08-20 08:35:22 | Re: static libpq (and other libraries) overwritten on aix |
Previous Message | Peter Eisentraut | 2022-08-20 07:38:48 | Re: [RFC] building postgres with meson - v11 |