| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg16: XX000: could not find pathkey item to sort |
| Date: | 2023-10-09 05:41:36 |
| Message-ID: | CAMbWs4_B93iGoU_CfNHjbCAL_2T0LnEog2ftXyjBvMePLn3TAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 9, 2023 at 12:13 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I've now pushed the patch that trims off the Pathkeys for the ORDER BY
> / DISTINCT aggregates.
Thanks for pushing!
> Those results are a bit noisy. Perhaps a few more runs might yield
> more consistency, but it seems that there's not too much overhead to
> it. If I take the minimum value out of the 3 runs from each, it comes
> to about 1.5% extra time spent in planning. Perhaps that's OK.
I agree that the overhead is acceptable, especially it only happens in
USE_ASSERT_CHECKING builds.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-10-09 06:45:31 | Re: PGDOCS - add more links in the pub/sub reference pages |
| Previous Message | Amit Kapila | 2023-10-09 05:39:04 | Re: Synchronizing slots from primary to standby |