Update
Extension updates involve two levels: package updates (operating system level) and extension object updates (database level).
Update Packages
Use package managers to update extension packages:
Batch update using Pigsty:
Update Extension Objects
After package updates, extension objects in the database may need to be synchronized.
View Updatable Extensions
Execute Extension Update
View Update Paths
Important Notes
-
Backup first: Backup the database before updating extensions, especially for extensions involving data type changes.
-
Check compatibility: Some extension major version upgrades may be incompatible. Consult the extension’s upgrade documentation.
-
Preloaded extensions: If updating a preloaded extension (like
timescaledb), a database restart may be required after the update. -
Dependencies: If other extensions depend on the updated extension, update them in dependency order.
-
Replication environments: In master-slave replication environments, test updates on slaves first, then update the master after confirmation.
Common Issues
Update Failure
If ALTER EXTENSION UPDATE fails, it may be because:
- No available upgrade path
- Extension is in use
- Insufficient permissions
Rollback Update
PostgreSQL extensions typically don’t support direct rollback. To rollback:
- Restore from backup
- Or: Uninstall new version extension, install old version package, recreate extension