v15.0.2 Beta

[szaimen]

Nextcloud 35.0.2 is included

What's Changed

🐞 Fixed bugs

• fix(Nextcloud): temporarily disable lazy objects during upgrade by @szaimen in fix(Nextcloud): temporarily disable lazy objects during upgrade #8957

👒 Updated dependencies

• build(deps): bump nextcloud/nextcloud-appapi-harp from v0.4.7 to v0.4.8 in /Containers/harp by @dependabot[bot] in build(deps): bump nextcloud/nextcloud-appapi-harp from v0.4.7 to v0.4.8 in /Containers/harp #8953
• build(deps): bump redis from 8.10.2-alpine to 8.10.3-alpine in /Containers/redis by @dependabot[bot] in build(deps): bump redis from 8.10.2-alpine to 8.10.3-alpine in /Containers/redis #8955
• build(deps): bump nats from 2.15.1-scratch to 2.15.2-scratch in /Containers/talk by @dependabot[bot] in build(deps): bump nats from 2.15.1-scratch to 2.15.2-scratch in /Containers/talk #8956
• PHP dependency updates by @github-actions[bot] in PHP dependency updates #8899
• build(deps): bump composer from 2.10.3 to 2.11.1 in /Containers/mastercontainer by @dependabot[bot] in build(deps): bump composer from 2.10.3 to 2.11.1 in /Containers/mastercontainer #8954
• Update test container image references by @github-actions[bot] in Update test container image references #8814

Full Changelog: v15.0.1...v15.0.2

---

This discussion was created from the release v15.0.2 Beta.

[vawaver]

AIO 15.0.2 Beta – Upgrade successful, PostgreSQL performance warning

Hi @szaimen,

First of all, some good news! After updating to AIO 15.0.2 Beta, the upgrade finally completed successfully, and my Nextcloud instance is running normally again.

The startup issue I originally reported in [AIO 15.0.0 Beta (#8895)](#8895) is now resolved. Thanks for the fix!

However, while checking the administration settings in Nextcloud Hub 26 Summer (35.0.2), I noticed a PostgreSQL performance warning under Administration settings → System.

The warning reports:

Dead tuples in user tables – Failing

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 suggested configuration snippet is:

# postgresql.conf
autovacuum_naptime = 30

Since PostgreSQL is managed by Nextcloud AIO, I'm not sure whether manually modifying postgresql.conf is the recommended approach or whether AIO already handles these settings.

Is this something I should address manually, or is there a recommended way to handle this within AIO?

I've attached screenshots of the warning and the suggested configuration.

Thanks for your guidance!

[szaimen]

Great to hear that the upsate succeeds!

The db thing should peobanly reported to https://github.com/nextcloud/serverinfo/issues

[vawaver]

Great to hear that the upsate succeeds!

The db thing should peobanly reported to https://github.com/nextcloud/serverinfo/issues

Reported here - nextcloud/serverinfo#1266