Sandro Santilli-2 wrote > Can you send the whole query ? > I think there's a class of such issues with big tables that need be > addressed (and secured with some automated testcase).
I did it again and - performance is ok - no idea what is going on there. :( >> This part of Qgis is for me like a Black Box: select your data and wait. >> No >> loggin, no infos, nothing. Just wait. > > You can open some of the box by connecting to the database > and looking at the pg_stat_activity table. will try it this night with another table. But: it would be much much easier if Qgis would do the Job: "log all queries sent to to the server" instead of using external tools to fetch that infos. Using pgadmin3, postgresql server logs, pg_stat_activity or even wireshark, which is for catching network traffic, is a little bit strange. > ... if something has to be fixed it has a chance to be in time for version > 2.6 > (due in 2 weeks). Thanks walter -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Trouble-with-PostGis-plugin-tp5166669p5166944.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
