O3-5697: Add indexes to queue_entry for queue_id, patient_id & started_at/ended_at - #116
Merged
NethmiRodrigo merged 3 commits intoAug 31, 2026
Merged
Conversation
|
jwnasambu
reviewed
Jul 22, 2026
jwnasambu
left a comment
jwnasambu
left a comment
There was a problem hiding this comment.
Thanks, @UjjawalPrabhat good and focused change.
jwnasambu
approved these changes
Jul 22, 2026
NethmiRodrigo
left a comment
NethmiRodrigo
left a comment
There was a problem hiding this comment.
Thanks @UjjawalPrabhat! Just one more thing -
queue_entry_patient_id_fk already indexes patient_id, so a name-based precondition would create a duplicate index on existing installs.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
queue_entrytable of Service Queues has no indexes on the columns those queries filter by (queue_id,patient_id,started_at,ended_at). Every query therefore scans the entire table.On a fresh demo install with a handful of patients this is invisible. But in a real clinic with months or years of accumulated queue history (potentially tens of thousands of rows), the queue page gets progressively slower until staff notice it taking seconds to load and by then the table is large enough that adding indexes needs careful migration planning. Indexing it now, while it's small, avoids that.
Related Issue
O3-5697