Bug report #7836
Inconsistent default estimation parameter between MSSQL and PostGIS
|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|
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?
#4 Updated by Giovanni Manghi 8 months ago
- Resolution set to end of life
- Status changed from Open to Closed
End of life notice: QGIS 2.18 LTR