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

Aperta
  • Qualcosa non va?
#1,266 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
postgresql
Ambito
databases, observability

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
JavaScript
Stelle
134
Fork
68
Merge medio
21h 28m
PR unite (30g)
53

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/serverinfo

Tutte le issue di nextcloud/serverinfo

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.