From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Implement multivariate n-distinct coefficients |
Date: | 2017-03-24 19:21:18 |
Message-ID: | 20170324192118.7cvlqhfx6p5ecdnd@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Why not use COSTS OFF? Or I'll put that even more strongly: all the
> existing regression tests use COSTS OFF, exactly to avoid this sort of
> machine-dependent output. There had better be a really damn good
> reason not to use it here.
If we use COSTS OFF, the test is completely pointless, as the plans look
identical regardless of whether the multivariate stats are being used or
not.
If we had a ROWS option to ANALYZE that showed estimated number of rows
but not the cost, that would be an option.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-03-24 19:35:54 | pgsql: Fix stats_ext test in 32 bit machines |
Previous Message | Tom Lane | 2017-03-24 19:09:54 | Re: Re: [COMMITTERS] pgsql: Implement multivariate n-distinct coefficients |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-03-24 19:30:12 | Re: ANALYZE command progress checker |
Previous Message | Corey Huinker | 2017-03-24 19:16:09 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |