| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Jakub Wartak <Jakub(dot)Wartak(at)tomtom(dot)com> |
| Subject: | Re: strange slow query - lost lot of time somewhere |
| Date: | 2022-05-10 02:22:48 |
| Message-ID: | 20220510022248.GU28830@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 03, 2022 at 02:13:18PM +1200, David Rowley wrote:
> I'm wishing I put the initial hash table size and the final hash table
> size in EXPLAIN + EXPLAIN ANALYZE now. Perhaps it's not too late for
> v15 to do that so that it might help us figure things out in the
> future.
On Fri, May 06, 2022 at 09:27:57PM +1200, David Rowley wrote:
> I'm very tempted to change the EXPLAIN output in at least master to
> display the initial and final (maximum) hash table sizes. Wondering if
> anyone would object to that?
No objection to add it to v15.
I'll point out that "Cache Mode" was added to EXPLAIN between 11.1 and 11.2
without controversy, so this could conceivably be backpatched to v14, too.
commit 6c32c0977783fae217b5eaa1d22d26c96e5b0085
Author: David Rowley <drowley(at)postgresql(dot)org>
Date: Wed Nov 24 10:07:38 2021 +1300
Allow Memoize to operate in binary comparison mode
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2022-05-10 02:54:57 | Re: psql now shows zero elapsed time after an error |
| Previous Message | Jonathan S. Katz | 2022-05-10 02:06:08 | Re: 2022-05-12 release announcement draft |