gitea/issue_pin.yml at 241f799edfecda763c7571ea33e82356b6689423 - gitea - Gitea

Mirrors/gitea

mirror of https://github.com/go-gitea/gitea.git synced 2025-02-25 21:35:23 +01:00

Lunny Xiao 7df09e31fa

Move issue pin to an standalone table for querying performance (#33452 )

Noticed a SQL in gitea.com has a bigger load. It seems both `is_pull`
and `pin_order` are not indexed columns in the database.

```SQL
SELECT `id`, `repo_id`, `index`, `poster_id`, `original_author`, `original_author_id`, `name`, `content`, `content_version`, `milestone_id`, `priority`, `is_closed`, `is_pull`, `num_comments`, `ref`, `pin_order`, `deadline_unix`, `created_unix`, `updated_unix`, `closed_unix`, `is_locked`, `time_estimate` FROM `issue` WHERE (repo_id =?) AND (is_pull = 0) AND (pin_order > 0) ORDER BY pin_order
```

I came across a comment
https://github.com/go-gitea/gitea/pull/24406#issuecomment-1527747296
from @delvh , which presents a more reasonable approach. Based on this,
this PR will migrate all issue and pull request pin data from the
`issue` table to the `issue_pin` table. This change benefits larger
Gitea instances by improving scalability and performance.

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>

2025-02-17 11:28:37 -08:00

7 lines

69 B

YAML

Raw Blame History

 -
   id: 1
   repo_id: 2
   issue_id: 4
   is_pull: false
   pin_order: 1