Update
Update extensions at two levels: packages in the operating system, and extension objects in the database.
Update Packages
Use package managers to update extension packages:
Use Pigsty to update packages on multiple nodes:
Update Extension Objects
After you update packages, you may also need to update the extension objects in the database.
View Updatable Extensions
Execute Extension Update
View Update Paths
Important Notes
Backup first: Back up the database before you update extensions. This is particularly important if the update changes data types.
Check compatibility: Some major version upgrades may be incompatible. Read the extension’s upgrade documentation.
Preloaded extensions: If you update a preloaded extension, such as
timescaledb, you may need to restart the database.Dependencies: If other extensions depend on the updated extension, update them in dependency order.
Replication environments: Test updates on replicas first. After you verify the results, update the primary.
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 usually do not support direct rollback. To roll back, use one of these methods:
- Restore from backup
- Uninstall the new extension version, install the old package version, and recreate the extension.
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)