Re: FW: Query execution failure

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 13:48:02
Message-ID: ZRWEEipzh80uCujz@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 27, 2023 at 10:27:34PM -0400, Bruce Momjian wrote:
> On Wed, Sep 27, 2023 at 09:06:13PM -0400, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > The attached patch documents this remote sort order requirement.
> >
> > That seems like quite a random place to insert the documentation.
> > I doubt that the requirement applies only to upper paths -- FDWs
> > are allowed to return sorted paths for base relations too,
> > comparable to indexscan paths.
>
> That is the only section of the docs that mentions sort pushdown.
> I don't see another reasonable location.

I now think the fdw docs are the wrong place for this since it is a user
requirement, not a developer one. I put it in CREATE SERVER, patch
attached.

--
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 604 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pantelis Theodosiou 2023-09-28 14:47:00 Re: BUG #18138: Using limit on VALUES causes type conversion to fail.
Previous Message PG Bug reporting form 2023-09-28 12:44:51 BUG #18138: Using limit on VALUES causes type conversion to fail.