↑↓ select ↵ open ⌫ change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

DocumentationVersion comparison

POSTGRESQL · VERSION COMPARE

PostgreSQL 9.0.2 release changes

All features, fixes, and compatibility notes in this release, with related records from other versions.

All changes in this release
All changes in this release

Includes changes after the source version through the target. A major version name means its initial release.

From PostgreSQL 9.0 onward: 17 major branches and 352 release notes. Updated 2026-09-26.

Complete release changes

9.0.2

2010-12-16

Export JSON
42changesFeatures, fixes, improvements
1releaseGrouped by release
0CVEsVulnerability IDs mentioned in these notes

9.0.2 HistoricalSupport ends 2015-10-08

PostgreSQL 9.0.2

Migration and compatibility

A dump/restore is not required for those running 9.0.X.

ImprovementsForce the default wal_sync_method to be fdatasync on Linux

Changes

Force the default wal_sync_method to be fdatasync on Linux (Tom Lane, Marti Raudsepp)

The default on Linux has actually been fdatasync for many years, but recent kernel changes caused PostgreSQL to choose open_datasync instead. This choice did not result in any performance improvement, and caused outright failures on certain filesystems, notably ext4 with the data=journal mount option.

Bug fixesFix "too many KnownAssignedXids" error during Hot Standby replay

Changes

Fix "too many KnownAssignedXids" error during Hot Standby replay (Heikki Linnakangas)

Bug fixesFix race condition in lock acquisition during Hot Standby

Changes

Fix race condition in lock acquisition during Hot Standby (Simon Riggs)

ImprovementsAvoid unnecessary conflicts during Hot Standby

Changes

Avoid unnecessary conflicts during Hot Standby (Simon Riggs)

This fixes some cases where replay was considered to conflict with standby queries (causing delay of replay or possibly cancellation of the queries), but there was no real conflict.

Bug fixesFix assorted bugs in WAL replay logic for GIN indexes

Changes

Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)

This could result in "bad buffer id: 0" failures or corruption of index contents during replication.

Bug fixesFix recovery from base backup when the starting checkpoint WAL record is not in the same WAL segment as its redo point

Changes

Fix recovery from base backup when the starting checkpoint WAL record is not in the same WAL segment as its redo point (Jeff Davis)

Bug fixesFix corner-case bug when streaming replication is enabled immediately after creating the master database cluster

Changes

Fix corner-case bug when streaming replication is enabled immediately after creating the master database cluster (Heikki Linnakangas)

Bug fixesFix persistent slowdown of autovacuum workers when multiple workers remain active for a long time

Changes

Fix persistent slowdown of autovacuum workers when multiple workers remain active for a long time (Tom Lane)

The effective vacuum_cost_limit for an autovacuum worker could drop to nearly zero if it processed enough tables, causing it to run extremely slowly.

Bug fixesFix long-term memory leak in autovacuum launcher

Changes

Fix long-term memory leak in autovacuum launcher (Alvaro Herrera)

ImprovementsAvoid failure when trying to report an impending transaction wraparound condition from outside a transaction

Changes

Avoid failure when trying to report an impending transaction wraparound condition from outside a transaction (Tom Lane)

This oversight prevented recovery after transaction wraparound got too close, because database startup processing would fail.

ImprovementsAdd support for detecting register-stack overrun on IA64

Changes

Add support for detecting register-stack overrun on IA64 (Tom Lane)

The IA64 architecture has two hardware stacks. Full prevention of stack-overrun failures requires checking both.

ImprovementsAdd a check for stack overflow in copyObject()

Changes

Add a check for stack overflow in copyObject() (Tom Lane)

Certain code paths could crash due to stack overflow given a sufficiently complex query.

Bug fixesFix detection of page splits in temporary GiST indexes

Changes

Fix detection of page splits in temporary GiST indexes (Heikki Linnakangas)

It is possible to have a "concurrent" page split in a temporary index, if for example there is an open cursor scanning the index when an insertion is done. GiST failed to detect this case and hence could deliver wrong results when execution of the cursor continued.

Bug fixesFix error checking during early connection processing

Changes

Fix error checking during early connection processing (Tom Lane)

The check for too many child processes was skipped in some cases, possibly leading to postmaster crash when attempting to add the new child process to fixed-size arrays.

ImprovementsImprove efficiency of window functions

Changes

Improve efficiency of window functions (Tom Lane)

Certain cases where a large number of tuples needed to be read in advance, but work_mem was large enough to allow them all to be held in memory, were unexpectedly slow. percent_rank(), cume_dist() and ntile() in particular were subject to this problem.

Bug fixesAvoid memory leakage while ANALYZE'ing complex index expressions

Changes

Avoid memory leakage while ANALYZE'ing complex index expressions (Tom Lane)

ImprovementsEnsure an index that uses a whole-row Var still depends on its table

Changes

Ensure an index that uses a whole-row Var still depends on its table (Tom Lane)

An index declared like create index i on t (foo(t.*)) would not automatically get dropped when its table was dropped.

ImprovementsAdd missing support in DROP OWNED BY for removing foreign data wrapper/server privileges belonging to a user

Changes

Add missing support in DROP OWNED BY for removing foreign data wrapper/server privileges belonging to a user (Heikki Linnakangas)

ImprovementsDo not "inline" a SQL function with multiple OUT parameters

Changes

Do not "inline" a SQL function with multiple OUT parameters (Tom Lane)

This avoids a possible crash due to loss of information about the expected result rowtype.

Bug fixesFix crash when inline-ing a set-returning function whose argument list contains a reference to an inline-able user function

Changes

Fix crash when inline-ing a set-returning function whose argument list contains a reference to an inline-able user function (Tom Lane)

ImprovementsBehave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is attached to the VALUES part of INSERT ... VALUES

Changes

Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is attached to the VALUES part of INSERT ... VALUES (Tom Lane)

ImprovementsMake the OFF keyword unreserved

Changes

Make the OFF keyword unreserved (Heikki Linnakangas)

This prevents problems with using off as a variable name in PL/pgSQL. That worked before 9.0, but was now broken because PL/pgSQL now treats all core reserved words as reserved.

Bug fixesFix constant-folding of COALESCE() expressions

Changes

Fix constant-folding of COALESCE() expressions (Tom Lane)

The planner would sometimes attempt to evaluate sub-expressions that in fact could never be reached, possibly leading to unexpected errors.

Bug fixesFix "could not find pathkey item to sort" planner failure with comparison of whole-row Vars

Changes

Fix "could not find pathkey item to sort" planner failure with comparison of whole-row Vars (Tom Lane)

Bug fixesFix postmaster crash when connection acceptance (accept() or one of the calls made immediately after it) fails, and the postmaster was compiled with GSSAPI support

Changes

Fix postmaster crash when connection acceptance (accept() or one of the calls made immediately after it) fails, and the postmaster was compiled with GSSAPI support (Alexander Chernikov)

ImprovementsRetry after receiving an invalid response packet from a RADIUS authentication server

Changes

Retry after receiving an invalid response packet from a RADIUS authentication server (Magnus Hagander)

This fixes a low-risk potential denial of service condition.

Bug fixesFix missed unlink of temporary files when log_temp_files is active

Changes

Fix missed unlink of temporary files when log_temp_files is active (Tom Lane)

If an error occurred while attempting to emit the log message, the unlink was not done, resulting in accumulation of temp files.

ImprovementsAdd print functionality for InhRelation nodes

Changes

Add print functionality for InhRelation nodes (Tom Lane)

This avoids a failure when debug_print_parse is enabled and certain types of query are executed.

Bug fixesFix incorrect calculation of distance from a point to a horizontal line segment

Changes

Fix incorrect calculation of distance from a point to a horizontal line segment (Tom Lane)

This bug affected several different geometric distance-measurement operators.

Bug fixesFix incorrect calculation of transaction status in ecpg

Changes

Fix incorrect calculation of transaction status in ecpg (Itagaki Takahiro)

Bug fixesFix errors in psql's Unicode-escape support

Changes

Fix errors in psql's Unicode-escape support (Tom Lane)

PerformanceSpeed up parallel pg_restore when the archive contains many large objects (blobs)

Changes

Speed up parallel pg_restore when the archive contains many large objects (blobs) (Tom Lane)

Bug fixesFix PL/pgSQL's handling of "simple" expressions to not fail in recursion or error-recovery cases

Changes

Fix PL/pgSQL's handling of "simple" expressions to not fail in recursion or error-recovery cases (Tom Lane)

Bug fixesFix PL/pgSQL's error reporting for no-such-column cases

Changes

Fix PL/pgSQL's error reporting for no-such-column cases (Tom Lane)

As of 9.0, it would sometimes report "missing FROM-clause entry for table foo" when "record foo has no field bar" would be more appropriate.

Bug fixesFix PL/Python to honor typmod (i.e., length or precision restrictions) when assigning to tuple fields

Changes

Fix PL/Python to honor typmod (i.e., length or precision restrictions) when assigning to tuple fields (Tom Lane)

This fixes a regression from 8.4.

Bug fixesFix PL/Python's handling of set-returning functions

Changes

Fix PL/Python's handling of set-returning functions (Jan Urbanski)

Attempts to call SPI functions within the iterator generating a set result would fail.

Bug fixesFix bug in contrib/cube's GiST picksplit algorithm

Changes

Fix bug in contrib/cube's GiST picksplit algorithm (Alexander Korotkov)

This could result in considerable inefficiency, though not actually incorrect answers, in a GiST index on a cube column. If you have such an index, consider REINDEXing it after installing this update.

ImprovementsDon't emit "identifier will be truncated" notices in contrib/dblink except when creating new connections

Changes

Don't emit "identifier will be truncated" notices in contrib/dblink except when creating new connections (Itagaki Takahiro)

Bug fixesFix potential coredump on missing public key in contrib/pgcrypto

Changes

Fix potential coredump on missing public key in contrib/pgcrypto (Marti Raudsepp)

Bug fixesFix buffer overrun in contrib/pg_upgrade

Changes

Fix buffer overrun in contrib/pg_upgrade (Hernan Gonzalez)

Bug fixesFix memory leak in contrib/xml2's XPath query functions

Changes

Fix memory leak in contrib/xml2's XPath query functions (Tom Lane)

ImprovementsUpdate time zone data files to tzdata release 2010o for DST law changes in Fiji and Samoa; also historical corrections for Hong Kong.

Changes

Update time zone data files to tzdata release 2010o for DST law changes in Fiji and Samoa; also historical corrections for Hong Kong.

How is this comparison generated?

The comparison follows PostgreSQL release notes from just after the source through the target version. For a major upgrade, maintenance releases from each older branch are included only up to the next major release date, and never after the target date. A major version such as 18 means its initial release, 18.0. Previews and development snapshots are labeled separately.

Entries come from the original English manuals. Release coverage and commit evidence are verified against upstream sources. Every entry retains its complete explanation and source link. Categories aid browsing; read the full notes for impact, conditions, and migration steps.

Fixes can be backported to several branches. Confirmed duplicates are merged conservatively, with every branch explanation retained. A note describing several independent fixes is excluded only when all are already present in the source. Major-release features remain distinct from related maintenance patches unless their complete original descriptions match. Uncertain matches are retained. This is a release-note history, not an exhaustive comparison of compiled binaries.

CVE results are calculated independently from the PostgreSQL security registry and vulnerability records. A CVE counts as gained protection only when the source is affected and the target is fixed or unaffected. Remaining vulnerabilities are listed separately. Security entries and distinct CVEs are counted separately.

Interaction inspired by pgversions.com and pgversionreport. Content comes from PostgreSQL release notes. See the release notes archive.