| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Renan Alves Fonseca <renanfonseca(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Remove restrictions in recursive query |
| Date: | 2025-03-27 16:39:55 |
| Message-ID: | CA+TgmoaD_hd-siBn4ROiXCZC=B0MasPDE2fisYD8SOOGWdE-Eg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 27, 2025 at 12:37 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> It's not a problem if UNION ALL is used within the initial_query and
> it's not a problem if UNION ALL is used within the iterated_query. But
> you can't apply ORDER BY to the result of the UNION, because the UNION
> is kind of fake -- we're not running the UNION as a single query,
> we're running the two halves separately, the first once and the second
> as many times as needed.
Oops. The two UNION ALL references in the first part of this paragraph
should have said ORDER BY.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-03-27 17:00:11 | Re: Remove restrictions in recursive query |
| Previous Message | Robert Haas | 2025-03-27 16:37:53 | Re: Remove restrictions in recursive query |