Database patch management
Oracle publishes Critical Patch Updates on the third Tuesday of January, April, July and October; the next are 19 Jan, 20 Apr, 20 Jul and 19 Oct 2027. PostgreSQL releases minor versions at least every three months. A database window follows those dates. Read 19 Nov 2026.
Oracle: four dates and revisions
Oracle states that Critical Patch Updates are collections of patches for multiple vulnerabilities, address flaws in Oracle code and in third-party components, are usually cumulative, and are available to customers with valid support contracts. A pre-release announcement appears on the Thursday before each release. The page also shows that an advisory is revised after release: the October 2026 update stood at Rev 3 on 4 Nov 2026, and the July 2026 update at Rev 7 on 20 Aug 2026 (Oracle). A policy should say that the revision history is reread, not only the release day, and that the deadline runs from the release unless stated otherwise.
Other engines
| Engine | Published rhythm and support | What the policy should note |
|---|---|---|
| PostgreSQL | Minor releases (security, low-risk and frequent bug fixes) at least once every three months; a critical fix may come out of cycle; each major version supported 5 years | Minor upgrades need no dump and restore: stop the server, install binaries, restart; read the release notes first |
| SQL Server | At least 10 years per version: 5 mainstream plus 5 extended; extended support includes only security updates; Extended Security Updates available up to three years past end of support | Past extended support, servicing stops; plan migration or paid ESU |
| Oracle Database | Quarterly Critical Patch Update dates above | Oracle says the patches are usually cumulative; confirm in each advisory that it covers the missed quarter |
Window, testing and rollback
Databases are usually patched in a restart window agreed with the application owner, and NIST's example maintenance groups record outage restrictions per group. Because a PostgreSQL minor release replaces binaries and restarts the server, the downtime is short; an Oracle quarterly update is larger and should be rehearsed on a clone first. Rollback is a restore or the previous software home: take a backup and record its identifier before the change. The sources read for this page do not document engine-level rollback, so the policy should require the backup, not assume the engine will reverse itself.
Evidence
- Patch level per instance after each cycle, against the quarterly advisory.
- The backup identifier and the restore test date.
- Instances on versions past their support end date, linked to the exceptions record in exceptions clause.
The dates feed the calendar in monitor for releases; the wording of the window is in maintenance windows.
Sources
- Oracle, Critical Patch Updates, Security Alerts and Bulletins, read 19 Nov 2026
- PostgreSQL, versioning policy, read 19 Nov 2026
- Microsoft Learn, SQL Server end of support options, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022), read 19 Nov 2026
Last reviewed 19 Nov 2026