Re: BUG #15882: Select .... UNION ALL - Mailing list pgsql-bugs

From David Rowley
Subject Re: BUG #15882: Select .... UNION ALL
Date
Msg-id CAKJS1f9ELmqOHz4dGc9a_t+0=x9q+zvjvRVvL-A3b92-ydH6Cw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15882: Select .... UNION ALL  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
On Tue, 2 Jul 2019 at 21:22, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> It occurs to me you are likely benefitting from the new parallel query infrastructure here.

Yeah, most likely.

It can be disabled globally by changing enable_parallel_append = off
in postgresql.conf. However, relying on the query outputting rows in
some order without an ORDER BY clause is asking for trouble. It looks
as though there are only 13 rows to sort, so I don't think an ORDER BY
will cost much.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-bugs by date:

Previous
From: Manuel Rigger
Date:
Subject: GROUP BY and inheritance issue
Next
From: Ilya Galdin
Date:
Subject: [libpq] Segmentation fault when call PQfinish inside singletone pattern