From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: EXPLAIN statement can also apply to SELECT INTO. |
Date: | 2023-08-22 05:06:44 |
Message-ID: | CAKFQuwaUufXMGiT8EikcLVsveWyM=aQjumVNg9D65zDMMMey_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday, August 21, 2023, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> hi.
>
> https://www.postgresql.org/docs/current/sql-explain.html
> >>>
> Any SELECT, INSERT, UPDATE, DELETE, MERGE, VALUES, EXECUTE, DECLARE,
> CREATE TABLE AS, or CREATE MATERIALIZED VIEW AS statement, whose
> execution plan you wish to see.
> >>>
>
> seems you can use it with SELECT INTO.
>
> explain (ANALYZE, BUFFERS, TIMING, VERBOSE ON, BUFFERS ON, WAL ON,SETTINGS
> ON)
> select count(*) as cnt INTO s from tenk1;
>
>
We try not to encourage such things. And CTAS is listed.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2023-08-22 05:18:56 | Re: Will PostgreSQL 16 supports native transparent data encryption ? |
Previous Message | jian he | 2023-08-22 05:03:31 | EXPLAIN statement can also apply to SELECT INTO. |