Skip to content

Add descending index for vulnerability reads group filters

What does this MR do and why?

Describe in detail what your merge request does and why.

Similar to !93535 (merged), but using a descending severity to address poor performance when using this ordering.

Noticed in !101703 (comment 1144901637).

Before: https://console.postgres.ai/shared/11be46fe-26f6-4bc5-b463-04ebfe31af8c

Time: 457.088 ms
  - planning: 7.178 ms
  - execution: 449.910 ms
    - I/O read: 0.000 ms
    - I/O write: 0.000 ms

Shared buffers:
  - hits: 79101 (~618.00 MiB) from the buffer pool
  - reads: 0 from the OS file cache, including disk I/O
  - dirtied: 0
  - writes: 0

After: https://console.postgres.ai/shared/41f5b312-29af-4d36-95fd-d12fd4acd903

Time: 272.212 ms
  - planning: 5.153 ms
  - execution: 267.059 ms
    - I/O read: 217.928 ms
    - I/O write: 0.000 ms

Shared buffers:
  - hits: 29585 (~231.10 MiB) from the buffer pool
  - reads: 667 (~5.20 MiB) from the OS file cache, including disk I/O
  - dirtied: 0
  - writes: 0

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Brian Williams

Merge request reports