May 14th, 2013· Writeable Foreign Tables, enabling pushing data to other databases
· pgsql_fdw driver for federation of PostgreSQL databases
· Automatically updatable VIEWs
· MATERIALIZED VIEW declaration
· LATERAL JOINs
· Additional JSON constructor and extractor functions
· Indexed regular expression search
· Disk page checksums to detect filesystem failures
· Fast failover to replicas for high availability
· Streaming-only remastering of replicas
· Performance and locking improvements for Foreign Key locks
· Parallel pg_dump for faster backups
· Directories for configuration files
· pg_isready database connection checker
· COPY FREEZE for reduced IO bulk loading
· User-defined background workers for automating database tasks
· Recursive view declaration
· lock_timeout directive
April 4th, 2013· Fix GiST indexes to not use "fuzzy" geometric comparisons for box, polygon, circle, and point columns
· Fix bugs in contrib/btree_gist for GiST indexes on text, bytea, bit, and numeric columns
· Fix bugs in page splitting code for multi-column GiST indexes
· Fix buffer leak in WAL replay causing "incorrect local pin count" errors
· Ensure crash recovery before entering archive recovery during unclean shutdown when recovery.conf is present
· Avoid deleting not-yet-archived WAL files during crash recovery
· Fix race condition in DELETE RETURNING
· Fix possible planner crash after adding columns to a view depending on another view
· Eliminate memory leaks in PL/Perl's spi_prepare() function
· Fix pg_dumpall to handle database names containing "=" correctly
· Avoid crash in pg_dump when an incorrect connection string is given
· Ignore invalid indexes in pg_dump and pg_upgrade
· Include only the current server version's subdirectory when backing up a tablespace with pg_basebackup
· Add a server version check in pg_basebackup and pg_receivexlog
· Fix contrib/dblink to handle inconsistent settings of DateStyle or IntervalStyle safely
· Fix contrib/pg_trgm's similarity() function to return zero for trigram-less strings
· Enable building PostgreSQL with Microsoft Visual Studio 2012
· Update time zone data files for DST law changes in Chile, Haiti, Morocco, Paraguay, and some Russian areas
February 7th, 2013· Prevent unnecessary table scans during vacuuming
· Prevent spurious cached plan error in PL/pgSQL
· Allow sub-SELECTs to be subscripted
· Prevent DROP OWNED from dropping databases or tablespaces
· Make ECPG use translated messages
· Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2
· Fix several activity log management issues on Windows
· Prevent autovacuum file truncation from being cancelled by deadlock_timeout
· Make extensions build with the .exe suffix automatically on Windows
· Fix concurrency issues with CREATE/DROP DATABASE
· Reject out-of-range values in to_date() conversion function
· Revert cost estimation for large indexes back to pre-9.2 behavior
· Make pg_basebackup tolerate timeline switches
· Cleanup leftover temp table entries during crash recovery
· Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor
· Prevent integer overflow in dynahash creation
· Make pg_upgrade work with INVALID indexes
· Fix bugs in TYPE privileges
· Allow Contrib installchecks to run in their own databases
· Many documentation updates
· Add new timezone "FET".
September 11th, 2012Improved Performance and Scalability:
· With the addition of linear scalability to 64 cores, index-only scans and reductions in CPU power consumption, PostgreSQL 9.2 has significantly improved scalability and developer flexibility for the most demanding workloads. Organizations like the U.S. Federal Aviation Administration and Heroku.com run applications on PostgreSQL, and HP has adopted it for their remote support software and to power their HP-UX/Itanium solutions.
· Improvements in vertical scalability increase PostgreSQL's ability to efficiently utilize hardware resources on larger servers. Advances in lock management, write efficiency, index-only access and other low-level operations allow the database engine to handle even larger-volume workloads.
Numerically, this means:
· Up to 350,000 read queries per second (more than 4X faster)
· Index-only scans for data warehousing queries (2–20X faster)
· Up to 14,000 data writes per second (5X faster)
· Also, the addition of cascading replication enables users to run even larger stacks of horizontally scaled servers under PostgreSQL 9.2.
· "NewsBlur, a social news reader, relies on Postgres for storing millions of sites and subscriptions. Solid and reliable for years," said Samuel Clay, founder of newsblur.com. "We're consistently on the bleeding edge (9.1 now, moving to 9.2 soon for the cascading replication alone) and it's been a pleasure since 8.4."
Flexible Developer Support:
· The flexibility of PostgreSQL is reflected in the diversity of organisations that have adopted it. For example NASA, the Chicago Mercantile Exchange and Instagram all rely on it to perform mission-critical applications. Version 9.2 extends this flexibility even further by including support for Range Types and JSON, allowing developers to use PostgreSQL in completely new ways.
· Range Types allow developers to create better calendaring, scientific, and financial applications. No other major SQL database supports this feature, which enables intelligent handling of blocks of time and numbers.
· With PostgreSQL 9.2, query results can be returned as JSON data types. Combined with the new PL/V8 Javascript and PL/Coffee database programming extensions, and the optional HStore key-value store, users can now utilize PostgreSQL like a "NoSQL" document database, while retaining PostgreSQL's reliability, flexibility and performance.
· "Native JSON support in PostgresSQL provides an efficient mechanism for creating and storing documents for web APIs. We use front-end libraries like jQuery to request tabular and tree-structured data; and the new features make it convenient and provide performance advantages in retrieving that data as JSON, " said Taras Mitran, Senior Architect, IVC Inc.
April 20th, 2011· fix build issues on HP-UX and Itanium
· update time zone files for recent time zone changes
· change SQLSTATE for Hot Standby warnings
· prevent bgwriter hang during recovery
· prevent recursive composite type creation
· disallow dropping tables whose triggers are still pending
· allow use of "replication" as a user name
· prevent a crash during GEQO planning
· improve join plans for tables with missing statistics
· fix error with SELECT FOR UPDATE in a subselect
· close PL/python array slice memory leak
· allow SSL connections for users with no home directory
· allow building PostgreSQL 9.0 with 64-bit MinGW
January 31st, 2011· Avoid failure when trying to report an impending transaction wraparound condition from outside a transaction. This oversight prevented recovery after transaction wraparound got too close, because database startup processing would fail, backpatched to all versions.
· Fix recovery from base backup when the starting checkpoint WAL record is not in the same WAL segment as its redo point, backpatched to all supported versions.
· Force default wal_sync_method to be fdatasync for Linux, backpatched to all supported versions.
· Fix memory leak with ANALYZE and complex index expressions, backpatched to all supported versions.
· Fix memory leak in contrib/xml2 functions, backpatched to all supported versions.
· Fix for segfault in pgcrypto when attempting to access an undefined public key, backpatched to all supported versions.
· Prevent inlining an SQL function with multiple OUT parameters, backpatched to all supported versions.
· Fix bugs in WAL replay logic for GIN indexes, backpatched to 8.2.
· Fix segfault when accept() or a call made right after accepting a connection fails when server is compiled with GSSAPI support, backpatched to 8.3.
· Fix error handling in tempfile deletion with log_temp_files active, backpatched to 8.3.
· Prevent slowing of of autovacuum workers because of leakage in cost parameter over life of worker, backpatched to 8.3.
· Check for too many children before returning "okay to proceed", backpatched to 8.4.
· Improve performance of internal tuplestore structures for window functions, backpatched to 8.4.
August 10th, 2010· Report disk space error properly and do not load .psqlrc when using pg_upgrade;
· Allow full SSL certificate verification when host and hostaddr are both specified, backpatched to 8.4;
· Fix for pg_dump's handling of SQL/MED objects;
· Bugfix and performance improvement for scans of lossy GIN index pointers;
· Fix for possible page corruption in ALTER TABLE .. SET TABLESPACE;
· Properly replay CREATE TABLESPACE during crash recovery;
· Cleanup subtransactions in FOR loops, and avoid deep recursion when assigning XIDs to multiple levels of subtransactions, both backpatched to 8.0.
May 28th, 2009· In order to improve the usability of pg_standby, we have added "fast" and "smart" mode switches to the utility. This is an API change. The "smart" mode ensures that all logs are applied for zero data loss, while the "fast" mode is similar to prior behavior. The behavior of the trigger file has also changed. Developers of PostgreSQL administration tools should modify them to support the new API.
· Additionally, the following features and utilities were fixed or modified between Beta 1 and Beta 2
· SQL/XML
· PL/pgSQL
· pg_bench
· JOIN costing
· Encoding and collation handling
· SSL connections
· psql df
· Unicode escapes
· Parallel restore
· pg_dumpall
April 17th, 2009· Windowing Functions
· Common Table Expressions & Recursive Joins
· Default & Variadic parameters for functions
· Parallel Restore
· Column Permissions
· Per-database locale settings
· Improved hash indexes
· Improved join performance for EXISTS and NOT EXISTS queries
· Easier-to-use Warm Standby
· Free Space Map auto-tuning
· Visibility Map (reduces vacuum overhead)
· Version-aware psql (backslash commands)
· Support SSL certs for user authentication
· Per-function runtime statistics
· Easy editing of functions in psql
· New contrib modules: pg_stat_statements, auto_explain, citext, btree_gin
Find us on Google+
