Re: New EXPLAIN option: ALL - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: New EXPLAIN option: ALL
Date
Msg-id CAH2-WzmHPo5ReFZKcHvixx-HAiF8+j0syGCgH7pumY5y2v=Sew@mail.gmail.com
Whole thread Raw
In response to Re: New EXPLAIN option: ALL  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Tue, May 7, 2019 at 9:31 AM David Fetter <david@fetter.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fuzzy thinking in is_publishable_class
Next
From: Tom Lane
Date:
Subject: Re: make \d pg_toast.foo show its indices