Doing queries that use archieved and state_id at the same time is slow on patchwork 3.1

Open
#581 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python, sql
Domain
databases

Research direction

Start by locating the database schema or migration entry point for the patchwork_patch table and review how indexes are defined. Add the suggested index on state_id and archived, then verify that queries filtering on both columns use it and that the change is included in the project's database setup.

Written by the indexing model from the issue text.

Description

This is a low hanging fruit. Just creating this index solved the issue:

CREATE INDEX idx_patch_state_id_archived on patchwork_patch (state_id, archived);

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.