Thank you very much for the input , Shane and Paul. I forgot to mention one point: the point and the polygon tables reside in different databases and dblink is used for cross db query. Today, we imported the small table into the db where the polygon table is and the problem is gone. So it sounds like dblink might be the reason for the crashes. Any bug associated with dblink?
On the other hand, the database is not well tuned so that "select count(*) from PolyTbl" takes about 100 seconds, which is too slow for a table with only 3 million records. Any input on the performance issue of postgres? Thanks a lot John
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
