Title: PostgreSQL performance warning: 948,750 dead tuples after upgrading to Nextcloud 35.0.2 (AIO 15.0.2 Beta)

オープン
  • 何か問題がありますか？
#1,266 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
postgresql
領域
databases, observability

調査の方向性

Start by locating the pg.dead_tuples check and the code that generates its PostgreSQL configuration snippet; compare their behavior with related issue #1219. The report does not identify a specific incorrect result, so first establish whether the reported dead-tuple count or recommendation is wrong for an AIO-managed database. Done means the check and its recommendations accurately communicate the state and appropriate next steps.

索引モデルが issue の本文から書いたものです。

説明

0. Needs triage bug
Bug description

After successfully upgrading my Nextcloud AIO installation to 15.0.2 Beta, which includes Nextcloud Hub 26 Summer (35.0.2), I noticed a PostgreSQL performance warning in the system administration interface.

The upgrade itself completed successfully, and Nextcloud is running normally.

However, under Administration settings → System → Database → Performance, the following check is marked as failing:

Dead tuples in user tables

Warning · pg.dead_tuples

At least one user table has accumulated many dead tuples
— autovacuum may not be keeping up.

Largest table has 948750 dead tuples.

Tune autovacuum_naptime / autovacuum_vacuum_scale_factor,
or run VACUUM ANALYZE on the worst tables.

The interface also provides the following configuration snippet:

# postgresql.conf
autovacuum_naptime = 30

Since PostgreSQL is managed by Nextcloud AIO, I am unsure whether this setting should be modified manually or whether the warning indicates an issue with the database health check or its recommendations.

The displayed snippet also does not indicate the current value of autovacuum_naptime.

Steps to reproduce
  1. Run Nextcloud AIO 15.0.2 Beta with Nextcloud 35.0.2.
  2. Open Administration settings → System.
  3. Navigate to the database performance section.
  4. Observe the failing pg.dead_tuples check.
  5. Click Show config snippet to display the recommended PostgreSQL configuration.
Expected behavior

The database performance check should accurately reflect the database state and provide actionable recommendations appropriate for a managed PostgreSQL environment such as Nextcloud AIO.

Actual behavior

The check reports 948,750 dead tuples and recommends adjusting PostgreSQL autovacuum parameters or running VACUUM ANALYZE.

It is unclear whether this represents an actual database maintenance problem requiring intervention or whether the check or its recommendation needs adjustment.

Environment
  • Nextcloud: 35.0.2 – Hub 26 Summer
  • Nextcloud AIO: 15.0.2 Beta
  • Deployment: Docker / Nextcloud AIO
  • Host OS: Ubuntu 24.04 LTS (VM)
  • Database: PostgreSQL (AIO-managed container)
  • Affected check: pg.dead_tuples
  • Reported value: 948,750 dead tuples
  • Suggested configuration: autovacuum_naptime = 30
Additional context

I was referred to the Serverinfo repository by the Nextcloud AIO maintainer.

I also found a potentially related report, [nextcloud/serverinfo#1219](https://github.com/nextcloud/serverinfo/issues/1219), which mentions the same suggested autovacuum_naptime = 30 setting.

I would appreciate some guidance on whether this warning requires action in an AIO-managed PostgreSQL installation and, if so, what the appropriate approach would be.

Screenshots of the performance warning and the suggested configuration snippet are attached.

Image Image
主要言語
JavaScript
スター
133
フォーク
67
平均マージ
21時間 28分
マージ済み PR（30日）
53

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextcloud/serverinfo のほかの issue

nextcloud/serverinfo の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。