Daily · Article 01 · 3 min read
- Security
- Open source
PostgreSQL security update: why incremental backups need a new starting point
Follow-up to the November 12 release, rechecked on November 16 JST
Summary
Check the running version, the new full backup and the plan for moving off PostgreSQL 14.
Key facts
PostgreSQL, an open-source database that can store orders and account records, fixed 52 security issues in its November 12 announcement. The project advises operators who use incremental backups to take a new full backup after updating and base subsequent incremental backups on it. Version 14.25 is the final release in the 14 series. Project announcement

1. The installer and the server taking orders
Consider a fictional online shop. When a customer orders, the shop's app saves the order in a database. The supplier releases new software and the operations team installs it. The team then checks that the database handling real orders runs the new version. For example, the upstream fix for the 18 series is 18.7. A shop using a managed database asks its cloud provider which version is serving requests and when it switched.
| Stage | Who handles it | Evidence |
|---|---|---|
| Release the update | PostgreSQL developers | Official 18.7 release and fixes for other series |
| Switch to the update | Operations team or cloud provider | Verify per environment. Check the running server version and switch time |
| Follow up on backups | Backup operator | Verify where incremental backups are used. Check the new full backup time and what later incremental backups depend on |
- Stage
Release the update
- Who handles it
- PostgreSQL developers
- Stage
Switch to the update
- Who handles it
- Operations team or cloud provider
- Evidence
- Verify per environment. Check the running server version and switch time
- Stage
Follow up on backups
- Who handles it
- Backup operator
- Evidence
- Verify where incremental backups are used. Check the new full backup time and what later incremental backups depend on
The cat asks Q&A
- The researcher
The dashboard says installation finished. Is the new version taking my orders now?
Pocket NotebookCheck the version running on the database that actually handles the order. If other servers handle reads, ask which of those have switched too.
2. Why start from a new full backup?
A full backup holds a copy at a point in time. An incremental backup saves changes since a backup it depends on. Suppose the shop copies all products and orders on Monday, then saves changes on Tuesday and Wednesday. Restoring Wednesday's data requires the starting copy and the changes it depends on. The project says earlier incremental backup files may be corrupt. Updating the software on a running server leaves those existing backup files as they are. 18.7 backup guidance

The cat asks Q&A
- The researcher
Does switching to the new version repair yesterday's backup?
Pocket NotebookThe old file stays as it was. If you use incremental backups, make a new full one after the update and check which full backup each new incremental depends on.
3. A routine update and the end of a series
Going from 18 to 18.7 is an update within one major series. It requires no dump and reload of the entire database, though some features need follow-up work. An index works like a book's index, helping the database find entries quickly. The release notes tell operators to rebuild certain affected indexes. For PostgreSQL 14, applying 14.25 still leaves a move to a supported major version to plan.
| Where you are | What the project shipped | What operators check |
|---|---|---|
| Series 18, 17, 16 or 15 | Fixes in 18.7, 17.12, 16.16 and 15.20 | Release guidance for your series, including index and backup follow-up |
| Series 14 | 14.25 is the final release | Running version and a migration schedule to a supported series · Support policy |
| PostgreSQL 19 test environment | 19 RC 2 is a release candidate | Keep track of test and live environments and verify when stable becomes available · Project announcement |
- Where you are
Series 18, 17, 16 or 15
- What the project shipped
- Fixes in 18.7, 17.12, 16.16 and 15.20
- What operators check
- Release guidance for your series, including index and backup follow-up
- Where you are
Series 14
- What the project shipped
- 14.25 is the final release
- What operators check
- Running version and a migration schedule to a supported series · Support policy
- Where you are
PostgreSQL 19 test environment
- What the project shipped
- 19 RC 2 is a release candidate
- What operators check
- Keep track of test and live environments and verify when stable becomes available · Project announcement
The cat asks Q&A
- The researcher
If customers can place orders, can we mark backup verification as done?
Pocket NotebookA successful order proves the live database responded. Ask the backup operator to verify a restore from the new full backup in a separate environment before you need it.
To close
Keep the update and restore records together
If different teams handle updates and backups, keep both confirmations in the same change record. During an outage, that record helps the team find the point it can restore to.
Sources
- PostgreSQL project announcementpostgresql.org
- PostgreSQL 18.7 release notespostgresql.org
- PostgreSQL support policypostgresql.org