[postgis-users] itemnquery limitation

Armin Burger armin.burger at libero.it
Sat Aug 9 06:08:29 PDT 2003


Paul, Zamil,

I experienced similar problems when using the PHP/MapScript function
'$layer->queryByRect()' for querying a layer with a rectangle
for the following combination
* PostGIS layer (PG both on Win and Linux)
* Win binary for Mapserver 4.0 final

Typically, when getting more than about 27 or 28 records the php.exe on
Win started to hang and the process had to be killed manually.

This problem occured only in the mentioned combination. It did not appear
when using MapServer Win binary 3.6 or running MapServer 4.0 on Linux.
Nor did I have this  problem with a shapefile (using any combination).

The error seems to be related to the function
$layer->getShape()
i.e. when printing out the values, the 'queryByRect()' itself was still
working fine.

I posted this problem on the MapServer list and Assefa Yewondwossen had a
look at it but could not reproduce the error.

Armin



> Not really. If you want us to fix it, you are really going to have to
> send us data so we can reproduce the problem. Which is a way of saying
> "no, we've never seen it before, help us see it so we can debug it" :)
> Paul

> Zamil Murji wrote:

>> That didn't cause the postgresql to crash just my user session.... No
>> matter how big my query area, I always get a maximum of 41 search
>> results returned. Any below this number works fine (and fast btw :)),
>> When it reaches 41 it just sits and hangs until I receive a premature
>> EOF.
>>
>> The exact query in postgres always returns more than 41 search
>> results. Have you guys had this same problem? This is when
>> mode=nquery.
>>
>> Hope this helps you guys fix the problems. Zamil
>>
>>
>>
>> -----Original Message----- From: David Blasby
>> [mailto:dblasby at refractions.net] Sent: Friday, August 08, 2003 11:43
>> AM To: PostGIS Users Discussion Subject: Re: [postgis-users]
>> itemnquery limitation
>>
>>
>> Zamil Murji wrote:
>>
>>> Sorry I jumped the gun. I had well_noded in the first query instead
>>> of well_node. SO, my fault!
>>
>>
>> that shouldnt cause the postgresql server to crash...
>>
>> dave
>>
>>
>> _______________________________________________ postgis-users mailing
>> list postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>> _______________________________________________ postgis-users mailing
>> list postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users


> --
>        __
>       /
>       | Paul Ramsey
>       | Refractions Research
>       | Email: pramsey at refractions.net
>       | Phone: (250) 885-0632
>       \_


> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users




More information about the postgis-users mailing list