| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Bruce Momjian <bruce(at)momjian(dot)us>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Default gucs for EXPLAIN |
| Date: | 2020-05-26 14:35:01 |
| Message-ID: | 20200526143501.GG3418@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Pavel Stehule (pavel(dot)stehule(at)gmail(dot)com) wrote:
> the partial solution can be custom psql statements. Now, it can be just
> workaround
>
> \set explain 'explain (analyze, buffers)'
> :explain select * from pg_class ;
>
> and anybody can prepare customized statements how he likes
Yeah, it's really very rudimentary though, unfortunately. A proper
language in psql would be *really* nice with good ways to reference
variables and such..
I don't view this as really being a good justification to not have a
\explain type of command.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-26 14:43:31 | Re: hash join error improvement (old) |
| Previous Message | Stephen Frost | 2020-05-26 14:32:06 | Re: Default gucs for EXPLAIN |