Re: Bogus ANALYZE results for an otherwise-unique column with many nulls

På søndag 07. august 2016 kl. 09:01:40, skrev Dean Rasheed <
dean(dot)a(dot)rasheed(at)gmail(dot)com <mailto:dean(dot)a(dot)rasheed(at)gmail(dot)com>>:
On 5 August 2016 at 21:48, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> OK, thanks.  What shall we do about Andreas' request to back-patch this?
> I'm personally willing to do it, but there is the old bugaboo of "maybe
> it will destabilize a plan that someone is happy with".
>

My inclination would be to back-patch it because arguably it's a
bug-fix -- at the very least the old behaviour didn't match the docs
for stadistinct:
[snip]
 
 
Will this then make it into the soon-to-be-released 9.5.4?
 
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>