Notice Extensions

Extension Update Available

An installed PostgreSQL extension has a newer version available that should be applied for security and feature improvements.

What is this issue?

PostgreSQL extensions can be updated independently of PostgreSQL itself.
When a new version is available:

- The new code is installed (typically via package manager)
- The extension must be updated in the database
- Some updates require schema changes

Common extensions that receive updates:
- pg_stat_statements
- PostGIS
- pg_cron
- pgcrypto

Why it matters

Security Fixes

Updates often include security patches

Bug Fixes

Known issues resolved in newer versions

New Features

Improved functionality and performance

Compatibility

May be required for PostgreSQL upgrades

How PG Pilot detects it

```sql
SELECT
  name,
  installed_version,
  default_version,
  installed_version != default_version AS update_available
FROM pg_available_extensions
WHERE installed_version IS NOT NULL
  AND installed_version != default_version;
```

How to fix it

1

Review the changelog

Check what changed in the new version before updating.
Review the extension's release notes.

2

Update the extension

Update to the new version:

ALTER EXTENSION extension_name UPDATE;

Or update to a specific version:

ALTER EXTENSION extension_name UPDATE TO '2.0';
3

Verify the update

Confirm the new version is active:

SELECT * FROM pg_extension WHERE extname = 'extension_name';

Prevention

  • Monitor extension versions with PG Pilot
  • Include extension updates in maintenance schedules
  • Test updates in staging before production
  • Subscribe to extension security announcements

Related Features

Configuration Management

PostgreSQL Documentation