Hi,
On 2017-01-18 21:09:52 -0500, Tom Lane wrote:
> I wrote:
> > If you don't want an ORDER BY, maybe turn off enable_hashagg for
> > these queries? But you'll get the same plan either way.
>
> Or not ... I forgot it has a better model of the rowcount changes now:
> regression=# set enable_hash
I wrote:
> If you don't want an ORDER BY, maybe turn off enable_hashagg for
> these queries? But you'll get the same plan either way.
Or not ... I forgot it has a better model of the rowcount changes now:
regression=# explain SELECT few.dataa, count(*), min(id), max(id),
unnest('{1,1,3}'::int[]
Andres Freund writes:
> Termite is also failing due to differing row orders from the rest of the
> animals. I'd intentionally left those undefined, because I wanted some
> queries without an ORDER BY. Haven't decided what the best fix is yet.
Looks to me like all the bigendian critters are unhap
On 2017-01-18 19:34:52 -0500, Tom Lane wrote:
> Andres Freund writes:
> > Adapt python regression tests to 69f4b9c85f16.
>
> Drat. I tested everything *but* plpython. You too, evidently :-(
Yea. I had taken it out of my configure invoking script because of a
packaging bug a while back :(.
Term
Andres Freund writes:
> Adapt python regression tests to 69f4b9c85f16.
Drat. I tested everything *but* plpython. You too, evidently :-(
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription: