Re: BUG #13908: Query returns too few rows

On Thu, Feb 4, 2016 at 3:13 PM, David G. Johnston <
david.g.johnston@gmail.com> wrote:

> Tom, we really need you to chime in here.
>
> On Thu, Feb 4, 2016 at 2:58 PM, David G. Johnston <
> david.g.johnston@gmail.com> wrote:
>
>> Adding back the list so that everyone can see the latest finding.  Addin=
g
>> in the original bug block too...
>> =E2=80=8B
>>
>> The following bug has been logged on the website:
>>
>> Bug reference:      13908
>> Logged by:          Seth
>> Email address:      seth-p@outlook.com
>> PostgreSQL version: 9.5.0
>> Operating system:   Windows 10
>> Description:
>>
>>
>> *  ->  Unique  (cost=3D1497322.60..1501340.65 rows=3D267870 width=3D24) =
(actual
>> time=3D153375.583..154829.461 rows=3D415874 loops=3D1)*
>>
>>
>
> =E2=80=8BWithout running any DML I just got this result on the DISTINCT q=
uery...=E2=80=8B
>
> *=E2=80=8B  ->  Unique  (cost=3D1519634.64..1520973.99 rows=3D200 width=
=3D48) (actual
> time=3D161695.425..163174.422 rows=3D416075 loops=3D1)*
> =E2=80=8B
>

=E2=80=8BAccording to 9.3 this 416,075 count is the correct one - and I got=
 the
same count with and without distinct executed multiple times each.

=E2=80=8BMy next thought is to see which 300 or so rows that are being left=
 out in
9.5 appear in 9.3....=E2=80=8B

=E2=80=8BDavid J.=E2=80=8B