We are using OSGeo.PostgreSQL (new). I have just found that i have bigger problems than describet in first post. I have Map that contains layers from OSGeo.PostgreSQL connection, i made some Pan and Zoom commands (for about 1 minute) and mgserver.exe process became from 50 MB to 300 MB of size. I have same map build from SHP sources and it works good (process size is not increasing while browsing that map). So i guess it is really FDO provider or data provider related issue, mayby i am missing some configuration stuff in postgreSQL database?
Does anyone uses PostGIS as datasource and do not have such kind of problems? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jackie Ng Sent: Wednesday, August 18, 2010 8:52 AM To: [email protected] Subject: [mapguide-users] RE: featureService.SelectFeatures and memory consumption Is the provider OSGeo.PostGIS (old) or OSGeo.PostgreSQL (new)? The old provider has many bugs and hasn't been maintained in a while. - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/featureService-SelectFeatures-and-mem ory-consumption-tp5427455p5435161.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
