| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lack of possibility to specify CTAS TAM |
| Date: | 2024-07-31 07:27:15 |
| Message-ID: | CAKFQuwZytDmJnpKM=Zf5Cod3ymZaAUJEheZ==Qc+7bQqnLKcHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, July 31, 2024, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Wednesday, July 31, 2024, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>>
>>
>> The same storage specification feature can actually be supported for
>> CTAE (like CTAS but execute) and CREATE MATERIALIZED VIEW.
>>
>>
> On a related note, the description here seems outdated.
>
> https://www.postgresql.org/docs/current/runtime-config-
> client.html#GUC-DEFAULT-TABLE-ACCESS-METHOD
>
Nevermind, re-reading it I see it is correct. The others are all covered
by “create” while “select into” is called out because of its reliance on
the default.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2024-07-31 07:31:09 | Re: Lack of possibility to specify CTAS TAM |
| Previous Message | Peter Smith | 2024-07-31 07:25:39 | Re: Logical Replication of sequences |