06531e01c5
Our experiments have shown that PostgreSQL 9.4 makes bad planning decisions about: - joining the layer tree to feature versions and feature - joining the feature versions to affected/fixed feature version and vulnerabilities It would for instance do a merge join between affected feature versions (300 rows, estimated 3000 rows) and fixed in feature version (100k rows). In this case, it is much more preferred to use a nested loop. |
||
|---|---|---|
| .. | ||
| migrations | ||
| testdata | ||
| complex_test.go | ||
| feature_test.go | ||
| feature.go | ||
| keyvalue_test.go | ||
| keyvalue.go | ||
| layer_test.go | ||
| layer.go | ||
| lock_test.go | ||
| lock.go | ||
| namespace_test.go | ||
| namespace.go | ||
| notification_test.go | ||
| notification.go | ||
| pgsql.go | ||
| queries.go | ||
| vulnerability_test.go | ||
| vulnerability.go | ||