Inconsistent default estimation parameter between MSSQL and PostGIS

[qgib]

Author Name: Aren Cambre (Aren Cambre)
Original Redmine Issue: 7836
Affected QGIS version: master
Redmine category:data_provider/mssql

---

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 #13513, 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?

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

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

---

• category_id was changed from Data Provider/PostGIS to Data Provider/MSSQL

[qgib]

Author Name: Paolo Cavallini (@pcav)

---

• fixed_version_id was changed from Version 2.0.0 to Future Release - High Priority

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• easy_fix was configured as 0
• regression was configured as 0

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

End of life notice: QGIS 2.18 LTR
*
Source:*
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

---

• resolution was changed from to end of life
• status_id was changed from Open to Closed