| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ORDER BY pushdowns seem broken in postgres_fdw |
| Date: | 2021-07-27 06:05:19 |
| Message-ID: | CAApHDvr1xyFoiVOMx0e4QDQjeuSWpbG9DNPLKx2Ur_uuuSNAQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 27 Jul 2021 at 17:20, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io> wrote:
> One thing in particular I was not sure about was how to fetch the operator
> associated with the path key ordering. I chose to go through the opfamily
> recorded on the member, but maybe locating the original SortGroupClause by its
> ref and getting the operator number here woud have worked. It seems more
> straightforward like this though.
I spent a bit of time trying to find a less invasive way of doing that
and didn't manage to come up with anything. I'm interested to hear if
anyone else has any better ideas.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-07-27 06:06:05 | Re: Inaccurate error message when set fdw batch_size to 0 |
| Previous Message | David Rowley | 2021-07-27 06:02:10 | Re: ATTACH PARTITION locking documentation for DEFAULT partitions |