Re: BUG #18381: Invalid query generated by postgres_fdw with UNION ALL and ORDER BY

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: michal(at)kleczek(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18381: Invalid query generated by postgres_fdw with UNION ALL and ORDER BY
Date: 2024-03-07 11:32:15
Message-ID: CAApHDvo22M2MMVs7ujrWexG2f_2CGPzsV978h4ORpTTG6OKN5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 7 Mar 2024 at 23:35, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 18381
> Logged by: Michal Kleczek
> Email address: michal(at)kleczek(dot)org
> PostgreSQL version: 16.2
> Operating system: Linux
> Description:

I see you've raised this on -hackers [1] already. Since there's
already some discussion and a proposed fix there, I think it's better
the discussion continues there.

David

[1] https://postgr.es/m/0714C8B8-8D82-4ABB-9F8D-A0C3657E7B6E@kleczek.org

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Maxim Orlov 2024-03-07 13:17:28 Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
Previous Message Ronan Dunklau 2024-03-07 11:21:24 Re: FSM Corruption (was: Could not read block at end of the relation)