| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pete Storer <Pete(dot)Storer(at)sas(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: FW: Query execution failure |
| Date: | 2023-01-30 15:34:20 |
| Message-ID: | Y9fjfNpP7HZh1YX9@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jan 26, 2023 at 11:06:41AM -0500, Tom Lane wrote:
> I don't know anything about the mysql FDW, but another possible route
> to fixing things is to get it to not believe that the remote's sort
> ordering matches the local one. If the plan were relying on a local
> sort instead of a remote sort then everything would be fine.
When we implemented sort pushdown to FDWs I had not considered how hard
it might be to match sort ordering, especially considering the problem
we have in matching orderings from different operating system versions.
Is this documented somewhere?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2023-01-30 16:16:03 | Re: FW: Query execution failure |
| Previous Message | David Rowley | 2023-01-30 12:36:21 | Re: range_agg extremely slow compared to naive implementation in obscure circumstances |