Re: BUG #19340: Wrong result from CORR() function - Mailing list pgsql-bugs

From Oleg Ivanov
Subject Re: BUG #19340: Wrong result from CORR() function
Date
Msg-id CAH1GMznwE=WGJYCZU1ou9iOmNR87NQFSRdYHqE3=JQ3as4P1hQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19340: Wrong result from CORR() function  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: BUG #19340: Wrong result from CORR() function
Re: BUG #19340: Wrong result from CORR() function
List pgsql-bugs
Yes, must be NULL in all the queries I have provided!
But PostgreSQL curr() returns numbers, wich is incorrect.

On Tue, Dec 2, 2025 at 2:30 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2025-12-02 at 07:57 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference:      19340
> Logged by:          Oleg Ivanov
> Email address:      o15611@gmail.com
> PostgreSQL version: 18.1
> Operating system:   all
> Description:       
>
> postgres=# SELECT corr( 0.09 , 0.09000001 ) FROM generate_series(1,24) ;
>  corr
> ------
>     
> (1 row)
>
> If argument is the constant, function CORR() must give a 0 or NaN.
> Consequences of this bug: statistic functions are used to make business
> descision. Wrong and completely different results can lead to make mistakes.

The documentation is pretty clear about that:

  In all cases, null is returned if the computation is meaningless, for example when N is zero.

Yours,
Laurenz Albe

pgsql-bugs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: BUG #19342: ERROR: function gcd(smallint, smallint) is not unique
Next
From: Laurenz Albe
Date:
Subject: Re: BUG #19341: REPLACE() fails to match final character when using nondeterministic ICU collation