Last checked and updated on April 16, 2026What Is New in PostgreSQL 7.2
| Category | Key Changes |
|---|---|
| New Features | Outer JOIN USING syntax, SQL92-compliant INFORMATION_SCHEMA, table functions, IPv6 support |
| Performance | Faster sorting, improved optimizer statistics, better index usage |
| Internationalization | Multi-byte character set support (EUC_JP, EUC_KR, EUC_CN, UNICODE) |
| Security | Password encryption via pg_shadow, new password authentication methods |
| Server Configuration | Runtime parameter changes without restart, new SET/SHOW commands |
| Monitoring | Enhanced logging options, session and query activity tracking |
What are the major SQL syntax improvements?
PostgreSQL 7.2 introduces SQL92 outer JOIN USING syntax, making queries more standard and readable. You can now write cleaner joins without repeating column names in the ON clause.
The new INFORMATION_SCHEMA provides standardized metadata access following SQL92 specifications. This means better compatibility with other database systems and applications that expect this standard interface.
Table functions allow returning multiple rows from functions, expanding what you can do with custom functions. This opens up new possibilities for data transformation and complex calculations directly in SQL.
How does performance improve in this release?
Sorting operations got significantly faster through optimized algorithms and memory management. Large result sets and ORDER BY operations will complete much quicker than previous versions.
The query optimizer now collects better statistics about table data distribution. This leads to smarter query plans and more effective index usage, especially for complex queries with multiple joins.
Index performance improvements mean better response times for data retrieval operations. The system makes smarter choices about when to use indexes versus sequential scans.
What internationalization features were added?
Multi-byte character set support includes EUC_JP, EUC_KR, EUC_CN, and UNICODE encoding. This enables proper storage and processing of Asian character sets without data corruption.
The enhanced locale support allows proper sorting and comparison of international text. This is crucial for applications serving global users with diverse language requirements.
Character set conversion between client and server happens automatically when needed. Applications can work with their preferred encoding while the database handles transparent conversion.
How is security enhanced in version 7.2?
Password encryption moved to pg_shadow system table with better protection mechanisms. Stored passwords are more secure against unauthorized access attempts.
New authentication methods provide flexibility in how clients connect to the database. You can choose the appropriate security level based on your network environment and trust boundaries.
IPv6 support means PostgreSQL can operate in modern networking environments. The database can accept connections from IPv6 addresses alongside traditional IPv4 connections.
What server management improvements should I know about?
Runtime parameter changes without server restart is a game-changer for administration. You can adjust settings like work_mem or shared_buffers on the fly while the database remains online.
The new SET and SHOW commands make configuration management more interactive. Database administrators can quickly view and modify settings without editing postgresql.conf directly.
Enhanced logging options provide better visibility into database operations. You can fine-tune what gets logged to balance between monitoring needs and storage consumption.
FAQ
How do I use the new OUTER JOIN USING syntax?
Replace traditional ON clauses with USING when joining on columns with the same name. For example: SELECT * FROM table1 LEFT JOIN table2 USING (common_id). This produces cleaner SQL that's easier to read and maintain.
Can I change configuration settings without restarting PostgreSQL?
Yes, many parameters can now be modified at runtime using SET commands. However, some settings still require restart, so check the documentation for specific parameters.
What's the benefit of the new INFORMATION_SCHEMA?
It provides standard SQL92-compliant views of database metadata. Applications written for other databases can now query PostgreSQL using the same metadata queries they use elsewhere.
How does IPv6 support work in practice?
PostgreSQL can now listen on IPv6 addresses if configured in postgresql.conf. You'll need to update your host-based authentication (pg_hba.conf) to include IPv6 address patterns alongside IPv4 rules.
Are there any backward compatibility concerns with this upgrade?
Most applications should work unchanged, but check any custom code that might rely on the old password encryption or metadata query methods. The new INFORMATION_SCHEMA might conflict with custom schemas named "information_schema".