[Bug]: Postgresql 15 (Debian12) does not allow user to create public tables - hence halting the Nextcloud 27 installation #39654
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
27-feedback
bug
feature: install and update
needs info
stale
Ticket or PR with no recent activity
Bug description
After installing the Debian 12, apache (or nginx), php, postgresql - at the first stage during the web install -
I get this message:
"Error
Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[42501]: Insufficient privilege: 7 ERROR: permission denied for schema public LINE 1: CREATE TABLE oc_migrations (app VARCHAR(255) NOT NULL, versi... ^
Create an admin account "
It seem this is an ISSUE with POSTGRESQL 15 (which is the default version in Debian 12) - there are reports that there are differences between Posgresql 14 and 15 ---- therefore the install scripts should be updated to address this issue.
Steps to reproduce
4.During the first web install - we get the error above halting the installation
it seem this is the issue which the new nextcloud installation script should consider as POSTGRESQL 15 public schema access is changed. The following link describes the differences between Postgresql 14 and 15.
https://www.cybertec-postgresql.com/en/error-permission-denied-schema-public/
Expected behavior
the web installer phase should go through after entering the login username password, database name, database user
Installation method
Community Manual installation with Archive
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: