| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Wrong results from Parallel Hash Full Join |
| Date: | 2023-04-19 17:16:24 |
| Message-ID: | ZEAh6CewmARbDVuN@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 19, 2023 at 11:17:04AM -0400, Melanie Plageman wrote:
> Ultimately this is probably fine. If we wanted to modify one of the
> existing tests to cover the multi-batch case, changing the select
> count(*) to a select * would do the trick. I imagine we wouldn't want to
> do this because of the excessive output this would produce. I wondered
> if there was a pattern in the tests for getting around this.
You could use explain (ANALYZE). But the output is machine-dependant in
various ways (which is why the tests use "explain analyze so rarely).
So you'd have to filter its output with a function (like the functions
that exist in a few places for similar purpose).
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-04-19 17:16:54 | Re: Direct I/O |
| Previous Message | Andres Freund | 2023-04-19 17:13:55 | Re: Direct I/O |