Hello,
I am using Postgre 9.3.4 with postgis 2.1.3
PostgreSQL 9.3.4, compiled by Visual C++ build 1600, 64-bit POSTGIS=2.1.3
r12547 GEOS=3.4.2-CAPI-1.8.2 r3924 PROJ=Rel. 4.8.0, 6 March 2012
GDAL=GDAL 1.10.0, released 2013/04/24 LIBXML=2.7.8 LIBJSON=UNKNOWN
RASTER
I have a spatial table
Hi,
The planner considers a seq scan is faster when only one record is expected.
You can disable seq scan for this query and force the index usage by
setting:
set enable_seqscan to off;
Nicolas
On 29 July 2014 12:05, Alex Reitbort a...@skylinesoft.com wrote:
Hello,
I am using Postgre
By the way, did you analyse the table ?
On 29 July 2014 12:23, Nicolas Ribot nicolas.ri...@gmail.com wrote:
Hi,
The planner considers a seq scan is faster when only one record is
expected.
You can disable seq scan for this query and force the index usage by
setting:
set enable_seqscan
Hey,
it would be a very bad idea to use
set enable_seqscan to off;
for other things that analyzing planner behaviour.
(in perticular, but not limited to , if you do other think that this simple
querry).
You may also want to check your postgres conf file regarding performances.
(and round a little
