| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: TRACE_SORT defined by default |
| Date: | 2019-04-25 15:53:16 |
| Message-ID: | CAMkU=1z2b-ykjz3Nh00g3L-2gn+zsFbRbQiNA_memnbYgJdZ_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 24, 2019 at 6:04 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Geoghegan <pg(at)bowt(dot)ie> writes:
>
> > In
> > any case the current status quo is that it's built by default. I have
> > used it in production, though not very often. It's easy to turn it on
> > and off.
>
> Would any non-wizard really have a use for it?
>
I've had people use it to get some insight into the operation and memory
usage of Aggregate nodes, since those nodes offer nothing useful via
EXPLAIN ANALYZE. It would be a shame to lose that ability on
package-installed PostgreSQL unless we fix Aggregate node reporting first.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-04-25 16:04:42 | Re: pg_waldump and PREPARE |
| Previous Message | Fujii Masao | 2019-04-25 15:36:16 | pg_waldump and PREPARE |