Bug report #7836

Inconsistent default estimation parameter between MSSQL and PostGIS

Added by Aren Cambre over 6 years ago. Updated 8 months ago.

Status:Closed
Priority:Normal
Assignee:-
Category:Data Provider/MSSQL
Affected QGIS version:master Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:end of life
Crashes QGIS or corrupts data:No Copied to github as #:16718

Description

Use estimated table parameters is enabled by default for MSSQL layers but Use estimated table metadata is disabled for PostGIS layers.

I previously asked for PostGIS to have estimation turned on by default in #3453, but it was shot down due to fear of bad estimates. But how likely will estimation produce unreliable results here? I still wonder if unreliable results is a boundary case? In the least, shouldn't we have consistent parameters for both DB types?

History

#1 Updated by Jürgen Fischer over 6 years ago

  • Category changed from Data Provider/PostGIS to Data Provider/MSSQL

the oracle and postgis provider don't use estimates by default.

#2 Updated by Paolo Cavallini almost 6 years ago

  • Target version changed from Version 2.0.0 to Future Release - High Priority

#3 Updated by Giovanni Manghi over 2 years ago

  • Easy fix? set to No
  • Regression? set to No

#4 Updated by Giovanni Manghi 8 months ago

  • Resolution set to end of life
  • Status changed from Open to Closed

Also available in: Atom PDF