Backup does not include PostgreSQL databases and users

[lxsdevcode]

Hi,

I’ve noticed that the backup system does not include PostgreSQL databases or their associated users.

The backup process completes without errors, but when restoring or inspecting the archive, both the PostgreSQL database data and the database users/roles are missing.

Steps to reproduce:
1. Create a PostgreSQL database
2. Create a PostgreSQL user and assign privileges
3. Add some test data
4. Run the backup process
5. Extract or restore the backup

Expected behavior:
The backup should include:
• PostgreSQL databases (data)
• PostgreSQL users/roles and their permissions

Actual behavior:
• PostgreSQL databases are not included
• PostgreSQL users/roles are not included

Environment:
• Panel version: v0.9-rc126
• OS: Debian 13
• PostgreSQL version: psql (PostgreSQL) 18.3 (Debian 18.3-1.pgdg13+1)

[shukiv]

Thanks for reporting this. You're right, the backup system currently only dumps MySQL databases and users. PostgreSQL is not included in the backup or restore flow yet.

This is on the roadmap. We'll add pg_dump support for PostgreSQL databases and pg_dumpall for roles/grants alongside the existing MySQL backup logic.

[shukiv]

Fixed in shukiv/jabali-backup@4d62b51.

Root cause: The PostgreSQL collector was searching for databases owned directly by the system username (e.g. shuki), but Jabali creates databases with the pattern {username}_{dbname} owned by derived users like {username}_{db_user} (e.g. shuki_admin). The ownership query never matched, so no databases were captured.

Changes:

Collector (lib/collectors/postgres.sh):

• Now searches for databases with LIKE '{username}\_%' prefix (matches the Jabali naming convention from app/Filament/Jabali/Pages/Databases.php)
• Captures all roles with the {username}_ prefix
• Exports roles via pg_dumpall --roles-only — this preserves SCRAM-SHA-256 password hashes as ALTER ROLE ... PASSWORD '...' statements, so passwords survive the restore without needing panel-side credential storage
• Captures per-database ownership to a .owner file so restore sets the correct owner

Restorer (lib/restorers/postgres.sh):

• Applies role definitions from the collector output, preserving original passwords
• Creates each database with the captured owner (falls back to postgres if owner role doesn't exist)
• Handles --force by dropping owned objects before recreating roles

Installer:

• install.sh now queues postgresql-client when a PostgreSQL server is detected on the host

Note on panel DB: Jabali does not persist PostgreSQL credentials in the panel database (unlike mysql_credentials). I followed that pattern — the restore relies on pg_dumpall password hashes rather than re-syncing from panel state.

Available after sudo jabali-backup update.