| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New EXPLAIN option: ALL |
| Date: | 2019-05-07 21:45:54 |
| Message-ID: | CAH2-WzmHPo5ReFZKcHvixx-HAiF8+j0syGCgH7pumY5y2v=Sew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 7, 2019 at 9:31 AM David Fetter <david(at)fetter(dot)org> wrote:
> If you're tuning a query interactively, it's a lot simpler to prepend,
> for example,
>
> EXPLAIN (ALL, FORMAT JSON)
>
> to it than to prepend something along the lines of
>
> EXPLAIN(ANALYZE, VERBOSE, COSTS, BUFFERS, SETTINGS, TIMING, SUMMARY, PARTRIDGE_IN_A_PEAR_TREE, FORMAT JSON)
>
> to it.
FWIW, I have the following in my psqlrc:
\set ea 'EXPLAIN (ANALYZE, SETTINGS, VERBOSE, BUFFERS) '
The idea behind that is that I can prepend ":ea" as needed, rather
than doing a lot of typing each time, as in:
:ea SELECT ...
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-05-07 21:49:41 | Re: make \d pg_toast.foo show its indices |
| Previous Message | Tom Lane | 2019-05-07 21:30:05 | Re: Fuzzy thinking in is_publishable_class |