Re: PGSQL 10.9 vs PGSQL 9.6 SQL query behaviour.

Hi  Jeff,

Thank you for suggestion, yes we tested without Pgsphere index ( dropped the index) in PGSQL 10.9 , run same SQL and got the expected result which is same as the one in PG 9.5 but different f when using the PG sphere in 10.9( which returned null rows),

explain SELECT count(*), min(degrees(long(pos))), max(degrees(long(pos))), min(degrees(lat(pos))), max(degrees(lat(pos)))
 FROM XXX.DR1
 WHERE pos <@ spoly '{(189.1d,30.9d),(192.1d,30.9d),(192.1d,33.9d),(189.1d,33.9d)}';
                                                                                           QUERY PLAN

------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------
 Aggregate  (cost=13576821.96..13576821.97 rows=1 width=40)
   ->  Seq Scan on DR1  (cost=0.00..13563681.20 rows=404331 width=16)
         Filter: (pos <@ '{(3.30041761552128 , 0.539306738866248),(3.35277749308111 , 0.539306738866248),(3.35277749308111 , 0.59166
6616426078),(3.30041761552128 , 0.591666616426078)}'::spoly)


________________________________
From: Jeff Janes <[email protected]>
Sent: Monday, October 21, 2019 3:20 PM
To: Ghiurea, Isabella
Cc: [email protected]
Subject: Re: PGSQL 10.9 vs PGSQL 9.6 SQL query behaviour.

On Mon, Oct 21, 2019 at 1:09 PM Ghiurea, Isabella <[email protected]<mailto:[email protected]>> wrote:

In PG 9,5.16 we are seeing the correct/expecting number of rows returned BUT in  in PG 10.9 we are seeing returns 0 rows.

If you disable the index (`set enable_bitmapscan=off` should do that) do you get the same answer on each server?

Cheer,

Jeff