| 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-09-28 01:00:12 |
| Message-ID: | ZRTQHKRhSLndfB5z@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jan 30, 2023 at 10:34:20AM -0500, Bruce Momjian wrote:
> 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?
The attached patch documents this remote sort order requirement.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| Attachment | Content-Type | Size |
|---|---|---|
| fdw.diff | text/x-diff | 995 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-09-28 01:06:13 | Re: FW: Query execution failure |
| Previous Message | Tom Lane | 2023-09-27 22:25:02 | Re: md5 password valid and invalid after upgrading |