| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] ALTER TABLE ... SET STORAGE default |
| Date: | 2022-08-22 13:15:39 |
| Message-ID: | CAN-LCVM1J-W5vRZGdtHAc+Drj+eQGYVsWBB6pU19sBYrW0RzJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers!
This seems a little bit confusing and thus very unfriendly for the user,
because the actual meaning
of the same 'DEFAULT' option will be different for each data type, and
to check storage mode user
has to query full table (or column) description.
I'd rather add a paragraph in documentation describing each data type
default storage mode.
On Mon, Aug 22, 2022 at 3:34 PM Aleksander Alekseev <
aleksander(at)timescale(dot)com> wrote:
> Hi hackers,
>
> I noticed that we support 'ALTER TABLE ... SET COMPRESSION default'
> syntax, but not 'SET STORAGE default' which seems to be a bit
> inconsistent. When the user changes the storage mode for a column
> there is no convenient way to revert the change.
>
> The proposed patch fixes this.
>
> --
> Best regards,
> Aleksander Alekseev
>
--
Regards,
Nikita Malakhov
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2022-08-22 13:28:15 | Re: [PATCH] ALTER TABLE ... SET STORAGE default |
| Previous Message | kuroda.hayato@fujitsu.com | 2022-08-22 12:49:53 | RE: Perform streaming logical transactions by background workers and parallel apply |