Project

General

Profile

Bug #19527

'messages' table can get large and can also get slow to query

Added by Ondřej Pražák almost 2 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Description of problem:

Querying the 'messages' table for an entry can take some time. For example, when we logged all queries over 1000msec for a user that uses openscap heavily, this query was about half of all logged queries:

SELECT "messages".*
FROM "messages"
WHERE "messages"."value" = <value>
AND "messages"."digest" = <digest>
AND "messages"."severity" = <sev>
AND "messages"."description" = <description>
AND "messages"."rationale" = <rationale>
ORDER BY "messages"."id" ASC
LIMIT 1

Associated revisions

Revision 75895fdd (diff)
Added by Ondřej Pražák over 1 year ago

Fixes #19527 - Clean report messages and prevent duplication

Revision f363f872
Added by Marek Hulán over 1 year ago

Merge pull request #257 from xprazak2/messages

Fixes #19527 - Clean report messages and prevent duplication

History

#1 Updated by The Foreman Bot almost 2 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ondřej Pražák
  • Pull request https://github.com/theforeman/foreman_openscap/pull/257 added

#2 Updated by Marek Hulán over 1 year ago

  • Subject changed from 'messages' table can get large and can also get slow to query to 'messages' table can get large and can also get slow to query
  • Legacy Backlogs Release (now unused) set to 245

#3 Updated by Ondřej Pražák over 1 year ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Ondřej Pražák about 1 year ago

  • Bugzilla link changed from 1438479 to 1520074

Also available in: Atom PDF