From: | Lahari Sengupta <jhinik8(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Discrepancy in query output |
Date: | 2018-02-22 16:05:03 |
Message-ID: | CAKEx41r1QzgUYNnOinsM9-ge_mx+Bux_GBBM8tNdGSvzunMHTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Ok. I tried to find out the extra row. And single with it returns true.
On Thu, Feb 22, 2018 at 5:54 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Thu, Feb 22, 2018 at 6:56 AM, Lahari Sengupta <jhinik8(at)gmail(dot)com>
> wrote:
>
>> Specially, if I remove the timing condition and want to select all from
>> servers then it misses one. How is it possible?
>>
>>>
>
>> st_distance(sv.geom, st.geom)<8.5) where
>>>
>>>
> ​Apparently st_distance() is non-deterministic in its output of float
> representations. Its seems likely (though I'm by no means fluent on
> floating-point concerns) to be a problem specific to the implementation of
> that function and thus better asked on a PostGIS list. You should identify
> the "extra" row and see if you can include it in a self-contained query
> that demonstrates occasionally returning false for the condition when
> normally it returns true.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | garret | 2018-02-27 17:59:22 | update tables with instead of trigger after update of view |
Previous Message | David G. Johnston | 2018-02-22 15:54:00 | Re: Discrepancy in query output |