Feature request #581
POSTGIS Layer feature count methodology
|Pull Request or Patch supplied:||Resolution:||fixed|
|Easy fix?:||No||Copied to github as #:||10640|
Currently in the win32 0.8 release (and any release that does not define the POSTGRESQL_THREADS macro) the POSTGIS data provider always does a full table count select. This is very annoying to the user who might have to wait some time when added a new layer that has millions of features.
A better solution is to use the pg_catalog information when the layer is first added then complete a full table count if required for later requirement. The layer properties could then just show that the count was estimated.
I believe this is the intended scenario if POSTGRESQL_THREADS is defined. So maybe the win32 version just needs to be compiled with thread support.
Also noted is that in the "thread section" current query is:
"select reltuples from pg_catalog.pg_class where relname = '" +
tableName + "'";
This should be changed to include the use of schemas:
QString sql = ""
"SELECT cls.reltuples "
"FROM pg_catalog.pg_class cls, "
" pg_catalog.pg_namespace nsp "
"WHERE cls.relname = '" + mTableName + "'"
"AND cls.relnamespace = nsp.oid "
"AND nsp.nspname = '" + mSchemaName + "'";
#1 Updated by Gavin Macaulay - about 14 years ago
Unfortunately, many parts of qgis require the feature count to be accurate at all times, and if not causes subtle errors in displaying feature and attribute data. For these reasons the POSTGRESQL_THREADS code has not been used since soon after it was written.
#2 Updated by anonymous - about 14 years ago
I think from a user’s point of view it is very annoying having to wait a long period just to load a layer - especially if it is just to view the feature and info features.
I believe the user would be ok with layer initially loading the layer with an estimated count and then having an immediate thread spawned off in the background to complete the full count.
Correct me if I'm wrong but aren’t feature retrieved independent of the layer count i.e. "getNextFeature". So the count should not apply in drawing and feature info functions.
Maybe these subtle areas of the application (i.e feature attribute table) could be explained (locked down?) to the user while the full count is carried out. I know this means more complication to the application and more work for the developers – but it would be very useful to users of large POSTGIS layers
#3 Updated by Maciej Sieczka - over 12 years ago
How does the issue look in QGIS 0.11? You can obtain it's Windows installer preview at: