Repository navigation
Postgres performance improvements #1248
Description
Tip
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
Is your feature request related to a problem? Please describe.
This is a request for enhancements in order to get better performance.
The nextcloud system reports that:
** Tables scanning sequentially **
Notice: pg.tables_without_index_use
pg.tables_without_index_use
Some tables have many sequential scans and no index scans, suggesting a missing index.
8 table(s) have > 1M sequential scans without any index scans.
oc_flow_operations
oc_ex_apps
oc_external_applicable
oc_share_external
oc_external_mounts
oc_group_admin
oc_external_config
oc_external_options
Add appropriate indexes to the affected tables (pg_stat_user_tables shows the full scan statistics).
Describe the solution you'd like
It could be useful to add the missing indices.
Describe alternatives you've considered
Keep on using the system as it is.
Additional context
Nextcloud version: 35.0.2.2
OS: Fedora 44
Activity
kesselb commentedon Nov 9, 2026
Thanks for reporting this, @marcello-lodi, and for listing the affected tables! This is the same check already tracked in #1157: it counts total sequential scans and doesn't look at table size. Small tables like these are read sequentially because that is the cheaper plan, so no indexes are missing here. I'm closing this as a duplicate to keep the discussion in one place. Feel free to subscribe to #1157 or give it a 👍.