From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: v12.0: ERROR: could not find pathkey item to sort |
Date: | 2019-10-11 14:48:37 |
Message-ID: | 17486.1570805317@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> I've reduced the failing query as much as possible to this:
> -- This is necessary to fail:
> SET enable_nestloop=off;
> SELECT * FROM
> (SELECT start_time, t1.site_id
> FROM pgw_kpi_view t1
> -- Apparently the where clause is necessary to fail...
> WHERE (start_time>='2019-10-10' AND start_time<'2019-10-11')
> -- The group by MAY be necessary to fail...
> GROUP BY 1,2
> ) AS data
> JOIN sites ON ( sites.site_location='' OR sites.site_office=data.site_id)
> The view is actually a join of two relkind=p partitioned tables (which I
> will acknowledge probably performs poorly).
Could you provide a self-contained test case please?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2019-10-11 15:12:28 | Re: stress test for parallel workers |
Previous Message | Justin Pryzby | 2019-10-11 14:37:03 | v12.0: ERROR: could not find pathkey item to sort |