arno/clair
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

pgsql: use subquery to plan GetNotification query (#182)

Browse Source 
This change enables the query planner to wait and sort the result set of
our query rather than attempting to re-use the layer table's index for
the ORDER BY clause. Because the result set is always small, this makes
queries that were previous tens of seconds, now tens of milliseconds.
This commit is contained in:
Jimmy Zelinskie 2016-05-20 13:10:00 -04:00
parent 51f9c5dcb4
commit 5d8336acb3
1 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
database/pgsql/queries.go
View File

@ -205,16 +205,22 @@ const (
WHERE name = $1` WHERE name = $1`
searchNotificationLayerIntroducingVulnerability = ` searchNotificationLayerIntroducingVulnerability = `
WITH subquery AS (
SELECT l.ID, l.name SELECT l.ID, l.name
FROM Vulnerability_Affects_FeatureVersion vafv, FeatureVersion fv, Layer_diff_FeatureVersion ldfv, Layer l FROM Vulnerability_Affects_FeatureVersion vafv, FeatureVersion fv, Layer_diff_FeatureVersion ldfv, Layer l
WHERE l.id >= $2 WHERE l.id >= $2
AND vafv.vulnerability_id = $1 AND vafv.vulnerability_id = $1
AND vafv.featureversion_id = fv.id AND vafv.featureversion_id = fv.id
AND ldfv.featureversion_id = fv.id AND ldfv.featureversion_id = fv.id
AND ldfv.modification = 'add' AND ldfv.modification = 'add'
AND ldfv.layer_id = l.id AND ldfv.layer_id = l.id
ORDER BY l.ID ORDER BY l.ID
LIMIT $3` )
SELECT *
FROM subquery
LIMIT $3;
`
// complex_test.go // complex_test.go
searchComplexTestFeatureVersionAffects = ` searchComplexTestFeatureVersionAffects = `