From: Tom Lane Date: Mon, 3 Oct 2005 16:04:51 +0000 (+0000) Subject: Update release notes for pending back-branch releases. X-Git-Tag: REL8_0_4~2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=65ae84279135711210a5d30cffb3298b1b6b66d3;p=postgresql Update release notes for pending back-branch releases. --- diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index a5ade504f3..41584ce24b 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,10 +1,100 @@ Release Notes + + + Release 8.0.4 + + + Release date + 2005-10-04 + + + + This release contains a variety of fixes from 8.0.3. + + + + Migration to version 8.0.4 + + + A dump/restore is not required for those running 8.0.X. However, + if you are upgrading from a version earlier than 8.0.3, see the release + notes for 8.0.3. + + + + + Changes + + +Fix error that allowed VACUUM to remove +ctid chains too soon, and add more checking in code that follows +ctid links +This fixes a long-standing problem that could cause crashes in very rare +circumstances. +Fix CHAR() to properly pad spaces to the specified +length when using a multiple-byte character set (Yoshiyuki Asaba) +In prior releases, the padding of CHAR() was incorrect +because it only padded to the specified number of bytes without +considering how many characters were stored. +Force a checkpoint before committing CREATE +DATABASE +This should fix recent reports of index is not a btree +failures when a crash occurs shortly after CREATE +DATABASE. +Handle consecutive embedded newlines in COPY +CSV-mode input +Fix date_trunc(week) for dates near year +end +Fix planning problem with outer-join ON clauses that reference +only the inner-side relation +Further fixes for x FULL JOIN y ON true corner +cases +Fix overenthusiastic optimization of x IN (SELECT +DISTINCT ...) and related cases +Fix mis-planning of queries with small LIMIT +values due to poorly thought out fuzzy cost +comparison +Make array_in and array_recv more +paranoid about validating their OID parameter +Fix missing rows in queries like UPDATE a=... WHERE +a... with GiST index on column a +Improve robustness of datetime parsing +Improve checking for partially-written WAL +pages +Improve robustness of signal handling when SSL is +enabled +Improve MIPS and M68K spinlock code +Don't try to open more than max_files_per_process +files during postmaster startup +Various memory leakage fixes +Various portability improvements +Update timezone data files +Improve handling of DLL load failures on Windows +Improve random-number generation on Windows +Make psql -f filename return a nonzero exit code +when opening the file fails +Change pg_dump to handle inherited check +constraints more reliably +Fix password prompting in pg_restore on +Windows +Fix PL/PgSQL to handle var := var correctly when +the variable is of pass-by-reference type +Fix PL/Perl %_SHARED so it's actually +shared +Fix contrib/pg_autovacuum to allow sleep +intervals over 2000 sec +Update contrib/tsearch2 to use current Snowball +code + + + + Release 8.0.3 @@ -41,7 +131,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.12 2005/05/09 00:10:06 tg The lesser problem is that the contrib/tsearch2 module - creates several functions that are misdeclared to return + creates several functions that are improperly declared to return internal when they do not accept internal arguments. This breaks type safety for all functions using internal arguments. @@ -275,8 +365,8 @@ statistics collector addresses in INET data types (Tom) - - + + Release 8.0.1 @@ -342,22 +432,23 @@ pg_dump/pg_restore typedefs (Michael) - - - - - Release 8.0 - - - Release date - 2005-01-19 - + + - - Overview + + Release 8.0 - - Major changes in this release: + + Release date + 2005-01-19 + + + + Overview + + + Major changes in this release: + @@ -507,21 +598,21 @@ typedefs (Michael) - - - - - Migration to version 8.0 - - - A dump/restore using pg_dump is - required for those wishing to migrate data from any previous - release. - - - - Observe the following incompatibilities: - + + + + Migration to version 8.0 + + + A dump/restore using pg_dump is + required for those wishing to migrate data from any previous + release. + + + + Observe the following incompatibilities: + + @@ -749,1947 +840,2009 @@ typedefs (Michael) - - + Deprecated Features - Some aspects of PostgreSQL's behavior - have been determined to be suboptimal. For the sake of backward - compatibility these have not been removed in 8.0, but they are - considered deprecated and will be removed in the next major - release. - - - - - - The 8.1 release will remove the to_char() function - for intervals. + Some aspects of PostgreSQL's behavior + have been determined to be suboptimal. For the sake of backward + compatibility these have not been removed in 8.0, but they are + considered deprecated and will be removed in the next major + release. - - + + - The server now warns of empty strings passed to - oid/float4/float8 data - types, but continues to interpret them as zeroes as before. - In the next major release, empty strings will be considered - invalid input for these data types. + The 8.1 release will remove the to_char() function + for intervals. + + + + + + The server now warns of empty strings passed to + oid/float4/float8 data + types, but continues to interpret them as zeroes as before. + In the next major release, empty strings will be considered + invalid input for these data types. + + + + + + By default, tables in PostgreSQL 8.0 + and earlier are created with OIDs. In the next release, + this will not be the case: to create a table + that contains OIDs, the - - - By default, tables in PostgreSQL 8.0 - and earlier are created with OIDs. In the next release, - this will not be the case: to create a table - that contains OIDs, the - - - - - - Changes - - - Below you will find a detailed account of the changes between - release 8.0 and the previous major release. - - - - Performance Improvements - - - - - Support cross-data-type index usage (Tom) - - - Before this change, many queries would not use an index if the data - types did not match exactly. This improvement makes index usage more - intuitive and consistent. - - - - - - New buffer replacement strategy that improves caching (Jan) - - - Prior releases used a least-recently-used (LRU) cache to keep - recently referenced pages in memory. The LRU algorithm - did not consider the number of times a specific cache entry was - accessed, so large table scans could force out useful cache pages. - The new cache algorithm uses four separate lists to track most - recently used and most frequently used cache pages and dynamically - optimize their replacement based on the work load. This should - lead to much more efficient use of the shared buffer cache. - Administrators who have tested shared buffer sizes in the past - should retest with this new cache replacement policy. - - - - - - Add subprocess to write dirty buffers periodically to reduce - checkpoint writes (Jan) - - - In previous releases, the checkpoint process, which runs every few - minutes, would write all dirty buffers to the operating system's - buffer cache then flush all dirty operating system buffers to - disk. This resulted in a periodic spike in disk usage that often - hurt performance. The new code uses a background writer to trickle - disk writes at a steady pace so checkpoints have far fewer dirty - pages to write to disk. Also, the new code does not issue a global - sync() call, but instead fsync()s just - the files written since the last checkpoint. This should improve - performance and minimize degradation during checkpoints. - - - - - - Add ability to prolong vacuum to reduce performance impact (Jan) - - - On busy systems, VACUUM performs many I/O - requests which can hurt performance for other users. This - release allows you to slow down VACUUM to - reduce its impact on other users, though this increases the - total duration of VACUUM. - - - - - - Improve B-tree index performance for duplicate keys (Dmitry Tkach, Tom) - - - This improves the way indexes are scanned when many duplicate - values exist in the index. - - - - - - Use dynamically-generated table size estimates while planning (Tom) - - - Formerly the planner estimated table sizes using the values seen - by the last VACUUM or ANALYZE, - both as to physical table size (number of pages) and number of rows. - Now, the current physical table size is obtained from the kernel, - and the number of rows is estimated by multiplying the table size - by the row density (rows per page) seen by the last - VACUUM or ANALYZE. This should - produce more reliable estimates in cases where the table size has - changed significantly since the last housekeeping command. - - - - - - Improved index usage with OR clauses (Tom) - - - This allows the optimizer to use indexes in statements with many OR - clauses that would not have been indexed in the past. It can also use - multi-column indexes where the first column is specified and the second - column is part of an OR clause. - - - - - - Improve matching of partial index clauses (Tom) - - - The server is now smarter about using partial indexes in queries - involving complex - - - - - Improve performance of the GEQO optimizer (Tom) - - - The GEQO optimizer is used to plan queries involving many tables (by - default, twelve or more). This release speeds up the way queries are - analyzed to decrease time spent in optimization. - - - - - - Miscellaneous optimizer improvements - - - There is not room here to list all the minor improvements made, but - numerous special cases work better than in prior releases. - - - - - - Improve lookup speed for C functions (Tom) - - - This release uses a hash table to lookup information for dynamically - loaded C functions. This improves their speed so they perform nearly as - quickly as functions that are built into the server executable. - - - - - - Add type-specific ANALYZE statistics - capability (Mark Cave-Ayland) - - - This feature allows more flexibility in generating statistics - for non-standard data types. - - - - - - ANALYZE now collects statistics for - expression indexes (Tom) - - - Expression indexes (also called functional indexes) allow users to - index not just columns but the results of expressions and function - calls. With this release, the optimizer can gather and use statistics - about the contents of expression indexes. This will greatly improve - the quality of planning for queries in which an expression index is - relevant. - - - - - - New two-stage sampling method for ANALYZE - (Manfred Koizar) - - - This gives better statistics when the density of valid rows is very - different in different regions of a table. - - - - - - Speed up TRUNCATE (Tom) - - - This buys back some of the performance loss observed in 7.4, while still - keeping TRUNCATE transaction-safe. - - - - - - - - - Server Changes - - - - - Add WAL file archiving and point-in-time recovery (Simon Riggs) - - - - - - Add tablespaces so admins can control disk layout (Gavin) - - - - - - Add a built-in log rotation program (Andreas Pflug) - - - It is now possible to log server messages conveniently without - relying on either syslog or an external log - rotation program. - - - - - - Add new read-only server configuration parameters to show server - compile-time settings: block_size, - integer_datetimes, max_function_args, - max_identifier_length, max_index_keys (Joe) - - - - - - Make quoting of sameuser, samegroup, and - all remove special meaning of these terms in - pg_hba.conf (Andrew) - - - - - - Use clearer IPv6 name ::1/128 for - localhost in default pg_hba.conf (Andrew) - - - - - - Use CIDR format in pg_hba.conf examples (Andrew) - - - - - - Rename server configuration parameters SortMem and - VacuumMem to work_mem and - maintenance_work_mem (Old names still supported) (Tom) - - - This change was made to clarify that bulk operations such as index and - foreign key creation use maintenance_work_mem, while - work_mem is for workspaces used during query execution. - - - - - - Allow logging of session disconnections using server configuration - log_disconnections (Andrew) - - - - - - Add new server configuration parameter log_line_prefix to - allow control of information emitted in each log line (Andrew) - - - Available information includes user name, database name, remote IP - address, and session start time. - - - - - - Remove server configuration parameters log_pid, - log_timestamp, log_source_port; functionality - superseded by log_line_prefix (Andrew) - - - - - - Replace the virtual_host and tcpip_socket - parameters with a unified listen_addresses parameter - (Andrew, Tom) - - - virtual_host could only specify a single IP address to - listen on. listen_addresses allows multiple addresses - to be specified. - - - - - - Listen on localhost by default, which eliminates the need for the - - - Listening on localhost (127.0.0.1) opens no new - security holes but allows configurations like Windows and JDBC, - which do not support local sockets, to work without special - adjustments. - - - - - - Remove syslog server configuration parameter, and add more - logical log_destination variable to control log output - location (Magnus) - - - - - - Change server configuration parameter log_statement to take - values all, mod, ddl, or - none to select which queries are logged (Bruce) - - - This allows administrators to log only data definition changes or - only data modification statements. - - - - - - Some logging-related configuration parameters could formerly be adjusted - by ordinary users, but only in the more verbose direction. - They are now treated more strictly: only superusers can set them. - However, a superuser may use ALTER USER to provide per-user - settings of these values for non-superusers. Also, it is now possible - for superusers to set values of superuser-only configuration parameters - via PGOPTIONS. - - - - - - Allow configuration files to be placed outside the data directory (mlw) - - - By default, configuration files are kept in the cluster's top directory. - With this addition, configuration files can be placed outside the - data directory, easing administration. - - - - - - Plan prepared queries only when first executed so constants can be - used for statistics (Oliver Jowett) - - - Prepared statements plan queries once and execute them many - times. While prepared queries avoid the overhead of re-planning - on each use, the quality of the plan suffers from not knowing the exact - parameters to be used in the query. In this release, planning of - unnamed prepared statements is delayed until the first execution, - and the actual parameter values of that execution are used as - optimization hints. This allows use of out-of-line parameter passing - without incurring a performance penalty. - - - - - - Allow DECLARE CURSOR to take parameters - (Oliver Jowett) - - - It is now useful to issue DECLARE CURSOR in a - Parse message with parameters. The parameter values - sent at Bind time will be substituted into the - execution of the cursor's query. - - - - - - Fix hash joins and aggregates of inet and - cidr data types (Tom) - - - Release 7.4 handled hashing of mixed inet and - cidr values incorrectly. (This bug did not exist - in prior releases because they wouldn't try to hash either - data type.) - - - - - - Make log_duration print only when log_statement - prints the query (Ed L.) - - - - - - - - - Query Changes - - - - - Add savepoints (nested transactions) (Alvaro) - - - - - - Unsupported isolation levels are now accepted and promoted to the - nearest supported level (Peter) - - - The SQL specification states that if a database doesn't support a - specific isolation level, it should use the next more restrictive level. - This change complies with that recommendation. - - - - - - Allow BEGIN WORK to specify transaction - isolation levels like START TRANSACTION does - (Bruce) - - - - - - Fix table permission checking for cases in which rules generate - a query type different from the originally submitted query (Tom) - - - - - - Implement dollar quoting to simplify single-quote usage (Andrew, Tom, - David Fetter) - - - In previous releases, because single quotes had to be used to - quote a function's body, the use of single quotes inside the - function text required use of two single quotes or other error-prone - notations. With this release we add the ability to use "dollar - quoting" to quote a block of text. The ability to use different - quoting delimiters at different nesting levels greatly simplifies - the task of quoting correctly, especially in complex functions. - Dollar quoting can be used anywhere quoted text is needed. - - - - - - Make CASE val WHEN compval1 THEN ... evaluate val only once (Tom) - - - - - - - - Test - - Fixes improper failure of cases such as SELECT SUM(win)/SUM(lose) - ... GROUP BY ... HAVING SUM(lose) > 0. This should work but formerly - could fail with divide-by-zero. - - - - - - Replace max_expr_depth parameter with - max_stack_depth parameter, measured in kilobytes of stack - size (Tom) - - - This gives us a fairly bulletproof defense against crashing due to - runaway recursive functions. Instead of measuring the depth of expression - nesting, we now directly measure the size of the execution stack. - - - - - - Allow arbitrary row expressions (Tom) - - - This release allows SQL expressions to contain arbitrary composite - types, that is, row values. It also allows functions to more easily - take rows as arguments and return row values. - - - - - - Allow - - - - - Avoid locale-specific case conversion of basic ASCII letters in - identifiers and keywords (Tom) - - - This solves the Turkish problem with mangling of words - containing I and i. Folding of characters - outside the 7-bit-ASCII set is still locale-aware. - - - - - - Improve syntax error reporting (Fabien, Tom) - - - Syntax error reports are more useful than before. - - - - - - Change EXECUTE to return a completion tag - matching the executed statement (Kris Jurka) - - - Previous releases return an EXECUTE tag for - any EXECUTE call. In this release, the tag - returned will reflect the command executed. - - - - - - Avoid emitting - - Such a clause makes no logical sense, but in some cases the rule - decompiler formerly produced this syntax. - - - - - - - - - Object Manipulation Changes - - - - - Add COMMENT ON for casts, conversions, languages, - operator classes, and large objects (Christopher) - - - - - - Add new server configuration parameter default_with_oids to - control whether tables are created with OIDs by default (Neil) - - - This allows administrators to control whether CREATE - TABLE commands create tables with or without OID - columns by default. (Note: the current factory default setting for - default_with_oids is TRUE, but the default - will become FALSE in future releases.) - - - - - - Add - - - - - Allow ALTER TABLE DROP COLUMN to drop an OID - column (ALTER TABLE SET WITHOUT OIDS still works) - (Tom) - - - - - - Allow composite types as table columns (Tom) - - - - - - Allow ALTER ... ADD COLUMN with defaults and - - - It is now possible for - - - - - Add ALTER COLUMN TYPE to change column's type (Rod) - - - It is now possible to alter a column's data type without dropping - and re-adding the column. - - - - - - Allow multiple ALTER actions in a single ALTER - TABLE command (Rod) - - - This is particularly useful for ALTER commands that - rewrite the table (which include - - - - - Allow ALTER TABLE to add SERIAL - columns (Tom) - - - This falls out from the new capability of specifying defaults for new - columns. - - - - - - Allow changing the owners of aggregates, conversions, databases, - functions, operators, operator classes, schemas, types, and tablespaces - (Christopher, Euler Taveira de Oliveira) - - - Previously this required modifying the system tables directly. - - - - - - Allow temporary object creation to be limited to - - - - - Add - - Prior to this release, there was no way to clear an auto-cluster - specification except to modify the system tables. - - - - - - Constraint/Index/SERIAL names are now - table_column_type - with numbers appended to guarantee uniqueness within the schema - (Tom) - - - The SQL specification states that such names should be unique - within a schema. - - - - - - Add pg_get_serial_sequence() to return a - SERIAL column's sequence name (Christopher) - - - This allows automated scripts to reliably find the SERIAL - sequence name. - - - - - - Warn when primary/foreign key data type mismatch requires costly lookup - - - - - - New ALTER INDEX command to allow moving of indexes - between tablespaces (Gavin) - - - - - - Make ALTER TABLE OWNER change dependent sequence - ownership too (Alvaro) - - - - - - - - - - Utility Command Changes - - - - - Allow CREATE SCHEMA to create triggers, - indexes, and sequences (Neil) - - - - - - Add - - This allows - - - - - Add - - This allows the LOCK command to fail if it - would have to wait for the requested lock. - - - - - - Allow COPY to read and write - comma-separated-value (CSV) files (Andrew, Bruce) - - - - - - Generate error if the COPY delimiter and NULL - string conflict (Bruce) - - - - - - GRANT/REVOKE behavior - follows the SQL spec more closely - - - - - - Avoid locking conflict between CREATE INDEX - and CHECKPOINT (Tom) - - - In 7.3 and 7.4, a long-running B-tree index build could block concurrent - CHECKPOINTs from completing, thereby causing WAL bloat because the - WAL log could not be recycled. - - - - - - Database-wide ANALYZE does not hold locks - across tables (Tom) - - - This reduces the potential for deadlocks against other backends - that want exclusive locks on tables. To get the benefit of this - change, do not execute database-wide ANALYZE - inside a transaction block (BEGIN block); it - must be able to commit and start a new transaction for each - table. - - - - - - REINDEX does not exclusively lock the index's - parent table anymore - - - The index itself is still exclusively locked, but readers of the - table can continue if they are not using the particular index - being rebuilt. - - - - - - Erase MD5 user passwords when a user is renamed (Bruce) - - - PostgreSQL uses the user name as salt - when encrypting passwords via MD5. When a user's name is changed, - the salt will no longer match the stored MD5 password, so the - stored password becomes useless. In this release a notice is - generated and the password is cleared. A new password must then - be assigned if the user is to be able to log in with a password. - - - - - - New pg_ctl - - Windows does not have a kill command to send signals to - backends so this capability was added to pg_ctl. - - - - - - Information schema improvements - - - - - - Add - - - - - Detect locale/encoding mismatch in - initdb (Peter) - - - - - - Add - - - - - - - - Data Type and Function Changes - - - - - More complete support for composite types (row types) (Tom) - - - Composite values can be used in many places where only scalar values - worked before. - - - - - - Reject non-rectangular array values as erroneous (Joe) - - - Formerly, array_in would silently build a - surprising result. - - - - - - Overflow in integer arithmetic operations is now detected (Tom) - - - - - - The arithmetic operators associated with the single-byte - "char" data type have been removed. - - - Formerly, the parser would select these operators in many situations - where an unable to select an operator error would be more - appropriate, such as null * null. If you actually want - to do arithmetic on a "char" column, you can cast it to - integer explicitly. - - - - - - Syntax checking of array input values considerably tightened up (Joe) - - - Junk that was previously allowed in odd places with odd results - now causes an ERROR, for example, non-whitespace - after the closing right brace. - - - - - - Empty-string array element values must now be written as - "", rather than writing nothing (Joe) - - - Formerly, both ways of writing an empty-string element value were - allowed, but now a quoted empty string is required. The case where - nothing at all appears will probably be considered to be a NULL - element value in some future release. - - - - - - Array element trailing whitespace is now ignored (Joe) - - - Formerly leading whitespace was ignored, but trailing whitespace - between an element value and the delimiter or right brace was - significant. Now trailing whitespace is also ignored. - - - - - - Emit array values with explicit array bounds when lower bound is not one - (Joe) - - - - - - Accept YYYY-monthname-DD as a date string (Tom) - - - - - - Make netmask and hostmask functions - return maximum-length mask length (Tom) - - - - - - Change factorial function to return numeric (Gavin) - - - Returning numeric allows the factorial function to - work for a wider range of input values. - - - - - - to_char/to_date() date conversion - improvements (Kurt Roeckx, Fabien Coelho) - - - - - - Make length() disregard trailing spaces in - CHAR(n) (Gavin) - - - This change was made to improve consistency: trailing spaces are - semantically insignificant in CHAR(n) data, so they - should not be counted by length(). - - - - - - Warn about empty string being passed to - OID/float4/float8 data types (Neil) - - - 8.1 will throw an error instead. - - - - - - Allow leading or trailing whitespace in - int2/int4/int8/float4/float8 - input routines - (Neil) - - - - - - Better support for IEEE Infinity and NaN - values in float4/float8 (Neil) - - - These should now work on all platforms that support IEEE-compliant - floating point arithmetic. - - - - - - Add - - - - - Fix to_char for 1 BC - (previously it returned 1 AD) (Bruce) - - - - - - Fix date_part(year) for BC dates (previously it - returned one less than the correct year) (Bruce) - - - - - - Fix date_part() to return the proper millennium and - century (Fabien Coelho) - - - In previous versions, the century and millennium results had a wrong - number and started in the wrong year, as compared to standard - reckoning of such things. - - - - - - Add ceiling() as an alias for ceil(), - and power() as an alias for pow() for - standards compliance (Neil) - - - - - - Change ln(), log(), - power(), and sqrt() to emit the correct - SQLSTATE error codes for certain error conditions, as - specified by SQL:2003 (Neil) - - - - - - Add width_bucket() function as defined by SQL:2003 (Neil) - - - - - - Add generate_series() functions to simplify working - with numeric sets (Joe) - - - - - - Fix upper/lower/initcap() functions to work with - multibyte encodings (Tom) - - - - - - Add boolean and bitwise integer - - - - - New session information functions to return network addresses for client - and server (Sean Chittenden) - - - - - - Add function to determine the area of a closed path (Sean Chittenden) - - - - - - Add function to send cancel request to other backends (Magnus) - - - - - - Add interval plus datetime operators (Tom) - - - The reverse ordering, datetime plus interval, - was already supported, but both are required by the SQL standard. - - - - - - Casting an integer to BIT(N) selects the rightmost N bits - of the integer - (Tom) - - - In prior releases, the leftmost N bits were selected, but this was - deemed unhelpful, not to mention inconsistent with casting from bit - to int. - - - - - - Require CIDR values to have all non-masked bits be zero - (Kevin Brintnall) - - - - - - - - - Server-Side Language Changes - - - - - In READ COMMITTED serialization mode, volatile functions - now see the results of concurrent transactions committed up to the - beginning of each statement within the function, rather than up to the - beginning of the interactive command that called the function. - - - - - - Functions declared STABLE or IMMUTABLE always - use the snapshot of the calling query, and therefore do not see the - effects of actions taken after the calling query starts, whether in - their own transaction or other transactions. Such a function must be - read-only, too, meaning that it cannot use any SQL commands other than - SELECT. There is a considerable performance gain from - declaring a function STABLE or IMMUTABLE - rather than VOLATILE. - - - - - - Non-deferred - - - - - Allow function parameters to be declared with names (Dennis Bjorklund) - - - This allows better documentation of functions. Whether the names - actually do anything depends on the specific function language - being used. - - - - - - Allow PL/pgSQL parameter names to be referenced in the function (Dennis Bjorklund) - - - This basically creates an automatic alias for each named parameter. - - - - - - Do minimal syntax checking of PL/pgSQL functions at creation time (Tom) - - - This allows us to catch simple syntax errors sooner. - - - - - - More support for composite types (row and record variables) in PL/pgSQL - - - For example, it now works to pass a rowtype variable to another function - as a single variable. - - - - - - Default values for PL/pgSQL variables can now reference previously - declared variables - - - - - - Improve parsing of PL/pgSQL FOR loops (Tom) - - - Parsing is now driven by presence of ".." rather than - data type of - - - - - Major overhaul of PL/Perl server-side language (Command Prompt, Andrew Dunstan) - - - - - - In PL/Tcl, SPI commands are now run in subtransactions. If an error - occurs, the subtransaction is cleaned up and the error is reported - as an ordinary Tcl error, which can be trapped with catch. - Formerly, it was not possible to catch such errors. - - - - - - Accept ELSEIF in PL/pgSQL (Neil) - - - Previously PL/pgSQL only allowed ELSIF, but many people - are accustomed to spelling this keyword ELSEIF. - - - - - - - - - <application>psql</> Changes - - - - - Improve psql information display about database - objects (Christopher) - - - - - - Allow psql to display group membership in - \du and \dg (Markus Bertheau) - - - - - - Prevent psql \dn from showing - temporary schemas (Bruce) - - - - - - Allow psql to handle tilde user expansion for file - names (Zach Irmen) - - - - - - Allow psql to display fancy prompts, including - color, via readline (Reece Hart, Chet Ramey) - - - - - - Make psql \copy match COPY command syntax - fully (Tom) - - - - - - Show the location of syntax errors (Fabien Coelho, Tom) - - - - - - Add CLUSTER information to psql - \d display - (Bruce) - - - - - - Change psql \copy stdin/stdout to read - from command input/output (Bruce) - - - - - - Add - - - - - Add global psql configuration file, psqlrc.sample - (Bruce) - - - This allows a central file where global psql startup commands can - be stored. - - - - - - Have psql \d+ indicate if the table - has an OID column (Neil) - - - - - - On Windows, use binary mode in psql when reading files so control-Z - is not seen as end-of-file - - - - - - Have \dn+ show permissions and description for schemas (Dennis - Bjorklund) - - - - - - Improve tab completion support (Stefan Kaltenbrunn, Greg Sabino Mullane) - - - - - - Allow boolean settings to be set using upper or lower case (Michael Paesold) - - - - - - - - - <application>pg_dump</> Changes - - - - - Use dependency information to improve the reliability of - pg_dump (Tom) - - - This should solve the longstanding problems with related objects - sometimes being dumped in the wrong order. - - - - - - Have pg_dump output objects in alphabetical order if possible (Tom) - - - This should make it easier to identify changes between - dump files. - - - - - - Allow pg_restore to ignore some SQL errors (Fabien Coelho) - - - This makes pg_restore's behavior similar to the - results of feeding a pg_dump output script to - psql. In most cases, ignoring errors and plowing - ahead is the most useful thing to do. Also added was a pg_restore - option to give the old behavior of exiting on an error. - - - - - - pg_restore - - - - - New begin/end markers in pg_dump text output (Bruce) - - - - - - Add start/stop times for - pg_dump/pg_dumpall in verbose mode - (Bruce) - - - - - - Allow most pg_dump options in - pg_dumpall (Christopher) - - - - - - Have pg_dump use ALTER OWNER rather - than SET SESSION AUTHORIZATION by default - (Christopher) - - - - - - - - - libpq Changes - - - - - Make libpq's - - - - - Add PQmbdsplen() which returns the display length - of a character (Tatsuo) - - - - - - Add thread locking to SSL and - Kerberos connections (Manfred Spraul) - - - - - - Allow PQoidValue(), PQcmdTuples(), and - PQoidStatus() to work on EXECUTE - commands (Neil) - - - - - - Add PQserverVersion() to provide more convenient - access to the server version number (Greg Sabino Mullane) - - - - - - Add PQprepare/PQsendPrepared() functions to support - preparing statements without necessarily specifying the data types - of their parameters (Abhijit Menon-Sen) - - - - - - Many ECPG improvements, including SET DESCRIPTOR (Michael) - - - - - - - - - Source Code Changes - - - - - Allow the database server to run natively on Windows (Claudio, Magnus, Andrew) - - - - - - Shell script commands converted to C versions for Windows support (Andrew) - - - - - - Create an extension makefile framework (Fabien Coelho, Peter) - - - This simplifies the task of building extensions outside the original - source tree. - - - - - - Support relocatable installations (Bruce) - - - Directory paths for installed files (such as the - /share directory) are now computed relative to the - actual location of the executables, so that an installation tree - can be moved to another place without reconfiguring and - rebuilding. - - - - - - Use - - - - - Add - - - - - Upgrade to DocBook V4.2 SGML (Peter) - - - - - - New PostgreSQL CVS tag (Marc) - - - This was done to make it easier for organizations to manage their - own copies of the PostgreSQL - CVS repository. File version stamps from the master - repository will not get munged by checking into or out of a copied - repository. - - - - - - Clarify locking code (Manfred Koizar) - - - - - - Buffer manager cleanup (Neil) - - - - - - Decouple platform tests from CPU spinlock code (Bruce, Tom) - - - - - - Add inlined test-and-set code on PA-RISC for gcc - (ViSolve, Tom) - - - - - - Improve i386 spinlock code (Manfred Spraul) - - - - - - Clean up spinlock assembly code to avoid warnings from newer - gcc releases (Tom) - - - - - - Remove JDBC from source tree; now a separate project - - - - - - Remove the libpgtcl client interface; now a separate project - - - - - - More accurately estimate memory and file descriptor usage (Tom) - - - - - - Improvements to the Mac OS X startup scripts (Ray A.) - - - - - - New fsync() test program (Bruce) - - - - - - Major documentation improvements (Neil, Peter) - - - - - - Remove pg_encoding; not needed - anymore - - - - - - Remove pg_id; not needed anymore - - - - - - Remove initlocation; not needed - anymore - - - - - - Auto-detect thread flags (no more manual testing) (Bruce) - - - - - - Use Olson's public domain timezone library (Magnus) - - - - - - With threading enabled, use thread flags on Unixware for - backend executables too (Bruce) - - - Unixware cannot mix threaded and non-threaded object files in the - same executable, so everything must be compiled as threaded. - - - - - - psql now uses a flex-generated - lexical analyzer to process command strings - - - - - - Reimplement the linked list data structure used throughout the - backend (Neil) - - - This improves performance by allowing list append and length - operations to be more efficient. - - - - - - Allow dynamically loaded modules to create their own server configuration - parameters (Thomas Hallgren) - - - - - - New Brazilian version of FAQ (Euler Taveira de Oliveira) - - - - - - Add French FAQ (Guillaume Lelarge) - - - - - - New pgevent for Windows logging - - - - - - Make libpq and ECPG build as proper shared libraries on OS X (Tom) - - - - - - - - - Contrib Changes - - - - - Overhaul of contrib/dblink (Joe) - - - - - - contrib/dbmirror improvements (Steven Singer) - - - - - - New contrib/xml2 (John Gray, Torchbox) - - - - - - Updated contrib/mysql - - - - - - New version of contrib/btree_gist (Teodor) - - - - - - New contrib/trgm, trigram matching for - PostgreSQL (Teodor) - - - - - - Many contrib/tsearch2 improvements (Teodor) - - - - - - Add double metaphone to contrib/fuzzystrmatch (Andrew) - - + + + + + Changes + + + Below you will find a detailed account of the changes between + release 8.0 and the previous major release. + + + + Performance Improvements + + + + + Support cross-data-type index usage (Tom) + + + Before this change, many queries would not use an index if the data + types did not match exactly. This improvement makes index usage more + intuitive and consistent. + + + + + + New buffer replacement strategy that improves caching (Jan) + + + Prior releases used a least-recently-used (LRU) cache to keep + recently referenced pages in memory. The LRU algorithm + did not consider the number of times a specific cache entry was + accessed, so large table scans could force out useful cache pages. + The new cache algorithm uses four separate lists to track most + recently used and most frequently used cache pages and dynamically + optimize their replacement based on the work load. This should + lead to much more efficient use of the shared buffer cache. + Administrators who have tested shared buffer sizes in the past + should retest with this new cache replacement policy. + + + + + + Add subprocess to write dirty buffers periodically to reduce + checkpoint writes (Jan) + + + In previous releases, the checkpoint process, which runs every few + minutes, would write all dirty buffers to the operating system's + buffer cache then flush all dirty operating system buffers to + disk. This resulted in a periodic spike in disk usage that often + hurt performance. The new code uses a background writer to trickle + disk writes at a steady pace so checkpoints have far fewer dirty + pages to write to disk. Also, the new code does not issue a global + sync() call, but instead fsync()s just + the files written since the last checkpoint. This should improve + performance and minimize degradation during checkpoints. + + + + + + Add ability to prolong vacuum to reduce performance impact (Jan) + + + On busy systems, VACUUM performs many I/O + requests which can hurt performance for other users. This + release allows you to slow down VACUUM to + reduce its impact on other users, though this increases the + total duration of VACUUM. + + + + + + Improve B-tree index performance for duplicate keys (Dmitry Tkach, Tom) + + + This improves the way indexes are scanned when many duplicate + values exist in the index. + + + + + + Use dynamically-generated table size estimates while planning (Tom) + + + Formerly the planner estimated table sizes using the values seen + by the last VACUUM or ANALYZE, + both as to physical table size (number of pages) and number of rows. + Now, the current physical table size is obtained from the kernel, + and the number of rows is estimated by multiplying the table size + by the row density (rows per page) seen by the last + VACUUM or ANALYZE. This should + produce more reliable estimates in cases where the table size has + changed significantly since the last housekeeping command. + + + + + + Improved index usage with OR clauses (Tom) + + + This allows the optimizer to use indexes in statements with many OR + clauses that would not have been indexed in the past. It can also use + multi-column indexes where the first column is specified and the second + column is part of an OR clause. + + + + + + Improve matching of partial index clauses (Tom) + + + The server is now smarter about using partial indexes in queries + involving complex + + + + + Improve performance of the GEQO optimizer (Tom) + + + The GEQO optimizer is used to plan queries involving many tables (by + default, twelve or more). This release speeds up the way queries are + analyzed to decrease time spent in optimization. + + + + + + Miscellaneous optimizer improvements + + + There is not room here to list all the minor improvements made, but + numerous special cases work better than in prior releases. + + + + + + Improve lookup speed for C functions (Tom) + + + This release uses a hash table to lookup information for dynamically + loaded C functions. This improves their speed so they perform nearly as + quickly as functions that are built into the server executable. + + + + + + Add type-specific ANALYZE statistics + capability (Mark Cave-Ayland) + + + This feature allows more flexibility in generating statistics + for non-standard data types. + + + + + + ANALYZE now collects statistics for + expression indexes (Tom) + + + Expression indexes (also called functional indexes) allow users to + index not just columns but the results of expressions and function + calls. With this release, the optimizer can gather and use statistics + about the contents of expression indexes. This will greatly improve + the quality of planning for queries in which an expression index is + relevant. + + + + + + New two-stage sampling method for ANALYZE + (Manfred Koizar) + + + This gives better statistics when the density of valid rows is very + different in different regions of a table. + + + + + + Speed up TRUNCATE (Tom) + + + This buys back some of the performance loss observed in 7.4, while still + keeping TRUNCATE transaction-safe. + + + + + + + + + Server Changes + + + + + Add WAL file archiving and point-in-time recovery (Simon Riggs) + + + + + + Add tablespaces so admins can control disk layout (Gavin) + + + + + + Add a built-in log rotation program (Andreas Pflug) + + + It is now possible to log server messages conveniently without + relying on either syslog or an external log + rotation program. + + + + + + Add new read-only server configuration parameters to show server + compile-time settings: block_size, + integer_datetimes, max_function_args, + max_identifier_length, max_index_keys (Joe) + + + + + + Make quoting of sameuser, samegroup, and + all remove special meaning of these terms in + pg_hba.conf (Andrew) + + + + + + Use clearer IPv6 name ::1/128 for + localhost in default pg_hba.conf (Andrew) + + + + + + Use CIDR format in pg_hba.conf examples (Andrew) + + + + + + Rename server configuration parameters SortMem and + VacuumMem to work_mem and + maintenance_work_mem (Old names still supported) (Tom) + + + This change was made to clarify that bulk operations such as index and + foreign key creation use maintenance_work_mem, while + work_mem is for workspaces used during query execution. + + + + + + Allow logging of session disconnections using server configuration + log_disconnections (Andrew) + + + + + + Add new server configuration parameter log_line_prefix to + allow control of information emitted in each log line (Andrew) + + + Available information includes user name, database name, remote IP + address, and session start time. + + + + + + Remove server configuration parameters log_pid, + log_timestamp, log_source_port; functionality + superseded by log_line_prefix (Andrew) + + + + + + Replace the virtual_host and tcpip_socket + parameters with a unified listen_addresses parameter + (Andrew, Tom) + + + virtual_host could only specify a single IP address to + listen on. listen_addresses allows multiple addresses + to be specified. + + + + + + Listen on localhost by default, which eliminates the need for the + + + Listening on localhost (127.0.0.1) opens no new + security holes but allows configurations like Windows and JDBC, + which do not support local sockets, to work without special + adjustments. + + + + + + Remove syslog server configuration parameter, and add more + logical log_destination variable to control log output + location (Magnus) + + + + + + Change server configuration parameter log_statement to take + values all, mod, ddl, or + none to select which queries are logged (Bruce) + + + This allows administrators to log only data definition changes or + only data modification statements. + + + + + + Some logging-related configuration parameters could formerly be adjusted + by ordinary users, but only in the more verbose direction. + They are now treated more strictly: only superusers can set them. + However, a superuser may use ALTER USER to provide per-user + settings of these values for non-superusers. Also, it is now possible + for superusers to set values of superuser-only configuration parameters + via PGOPTIONS. + + + + + + Allow configuration files to be placed outside the data directory (mlw) + + + By default, configuration files are kept in the cluster's top directory. + With this addition, configuration files can be placed outside the + data directory, easing administration. + + + + + + Plan prepared queries only when first executed so constants can be + used for statistics (Oliver Jowett) + + + Prepared statements plan queries once and execute them many + times. While prepared queries avoid the overhead of re-planning + on each use, the quality of the plan suffers from not knowing the exact + parameters to be used in the query. In this release, planning of + unnamed prepared statements is delayed until the first execution, + and the actual parameter values of that execution are used as + optimization hints. This allows use of out-of-line parameter passing + without incurring a performance penalty. + + + + + + Allow DECLARE CURSOR to take parameters + (Oliver Jowett) + + + It is now useful to issue DECLARE CURSOR in a + Parse message with parameters. The parameter values + sent at Bind time will be substituted into the + execution of the cursor's query. + + + + + + Fix hash joins and aggregates of inet and + cidr data types (Tom) + + + Release 7.4 handled hashing of mixed inet and + cidr values incorrectly. (This bug did not exist + in prior releases because they wouldn't try to hash either + data type.) + + + + + + Make log_duration print only when log_statement + prints the query (Ed L.) + + + + + + + + + Query Changes + + + + + Add savepoints (nested transactions) (Alvaro) + + + + + + Unsupported isolation levels are now accepted and promoted to the + nearest supported level (Peter) + + + The SQL specification states that if a database doesn't support a + specific isolation level, it should use the next more restrictive level. + This change complies with that recommendation. + + + + + + Allow BEGIN WORK to specify transaction + isolation levels like START TRANSACTION does + (Bruce) + + + + + + Fix table permission checking for cases in which rules generate + a query type different from the originally submitted query (Tom) + + + + + + Implement dollar quoting to simplify single-quote usage (Andrew, Tom, + David Fetter) + + + In previous releases, because single quotes had to be used to + quote a function's body, the use of single quotes inside the + function text required use of two single quotes or other error-prone + notations. With this release we add the ability to use "dollar + quoting" to quote a block of text. The ability to use different + quoting delimiters at different nesting levels greatly simplifies + the task of quoting correctly, especially in complex functions. + Dollar quoting can be used anywhere quoted text is needed. + + + + + + Make CASE val WHEN compval1 THEN ... evaluate val only once (Tom) + + + + + + + + Test + + Fixes improper failure of cases such as SELECT SUM(win)/SUM(lose) + ... GROUP BY ... HAVING SUM(lose) > 0. This should work but formerly + could fail with divide-by-zero. + + + + + + Replace max_expr_depth parameter with + max_stack_depth parameter, measured in kilobytes of stack + size (Tom) + + + This gives us a fairly bulletproof defense against crashing due to + runaway recursive functions. Instead of measuring the depth of expression + nesting, we now directly measure the size of the execution stack. + + + + + + Allow arbitrary row expressions (Tom) + + + This release allows SQL expressions to contain arbitrary composite + types, that is, row values. It also allows functions to more easily + take rows as arguments and return row values. + + + + + + Allow + + + + + Avoid locale-specific case conversion of basic ASCII letters in + identifiers and keywords (Tom) + + + This solves the Turkish problem with mangling of words + containing I and i. Folding of characters + outside the 7-bit-ASCII set is still locale-aware. + + + + + + Improve syntax error reporting (Fabien, Tom) + + + Syntax error reports are more useful than before. + + + + + + Change EXECUTE to return a completion tag + matching the executed statement (Kris Jurka) + + + Previous releases return an EXECUTE tag for + any EXECUTE call. In this release, the tag + returned will reflect the command executed. + + + + + + Avoid emitting + + Such a clause makes no logical sense, but in some cases the rule + decompiler formerly produced this syntax. + + + + + + + + + Object Manipulation Changes + + + + + Add COMMENT ON for casts, conversions, languages, + operator classes, and large objects (Christopher) + + + + + + Add new server configuration parameter default_with_oids to + control whether tables are created with OIDs by default (Neil) + + + This allows administrators to control whether CREATE + TABLE commands create tables with or without OID + columns by default. (Note: the current factory default setting for + default_with_oids is TRUE, but the default + will become FALSE in future releases.) + + + + + + Add + + + + + Allow ALTER TABLE DROP COLUMN to drop an OID + column (ALTER TABLE SET WITHOUT OIDS still works) + (Tom) + + + + + + Allow composite types as table columns (Tom) + + + + + + Allow ALTER ... ADD COLUMN with defaults and + + + It is now possible for + + + + + Add ALTER COLUMN TYPE to change column's type (Rod) + + + It is now possible to alter a column's data type without dropping + and re-adding the column. + + + + + + Allow multiple ALTER actions in a single ALTER + TABLE command (Rod) + + + This is particularly useful for ALTER commands that + rewrite the table (which include + + + + + Allow ALTER TABLE to add SERIAL + columns (Tom) + + + This falls out from the new capability of specifying defaults for new + columns. + + + + + + Allow changing the owners of aggregates, conversions, databases, + functions, operators, operator classes, schemas, types, and tablespaces + (Christopher, Euler Taveira de Oliveira) + + + Previously this required modifying the system tables directly. + + + + + + Allow temporary object creation to be limited to + + + + + Add + + Prior to this release, there was no way to clear an auto-cluster + specification except to modify the system tables. + + + + + + Constraint/Index/SERIAL names are now + table_column_type + with numbers appended to guarantee uniqueness within the schema + (Tom) + + + The SQL specification states that such names should be unique + within a schema. + + + + + + Add pg_get_serial_sequence() to return a + SERIAL column's sequence name (Christopher) + + + This allows automated scripts to reliably find the SERIAL + sequence name. + + + + + + Warn when primary/foreign key data type mismatch requires costly lookup + + + + + + New ALTER INDEX command to allow moving of indexes + between tablespaces (Gavin) + + + + + + Make ALTER TABLE OWNER change dependent sequence + ownership too (Alvaro) + + + + + + + + + + Utility Command Changes + + + + + Allow CREATE SCHEMA to create triggers, + indexes, and sequences (Neil) + + + + + + Add + + This allows + + + + + Add + + This allows the LOCK command to fail if it + would have to wait for the requested lock. + + + + + + Allow COPY to read and write + comma-separated-value (CSV) files (Andrew, Bruce) + + + + + + Generate error if the COPY delimiter and NULL + string conflict (Bruce) + + + + + + GRANT/REVOKE behavior + follows the SQL spec more closely + + + + + + Avoid locking conflict between CREATE INDEX + and CHECKPOINT (Tom) + + + In 7.3 and 7.4, a long-running B-tree index build could block concurrent + CHECKPOINTs from completing, thereby causing WAL bloat because the + WAL log could not be recycled. + + + + + + Database-wide ANALYZE does not hold locks + across tables (Tom) + + + This reduces the potential for deadlocks against other backends + that want exclusive locks on tables. To get the benefit of this + change, do not execute database-wide ANALYZE + inside a transaction block (BEGIN block); it + must be able to commit and start a new transaction for each + table. + + + + + + REINDEX does not exclusively lock the index's + parent table anymore + + + The index itself is still exclusively locked, but readers of the + table can continue if they are not using the particular index + being rebuilt. + + + + + + Erase MD5 user passwords when a user is renamed (Bruce) + + + PostgreSQL uses the user name as salt + when encrypting passwords via MD5. When a user's name is changed, + the salt will no longer match the stored MD5 password, so the + stored password becomes useless. In this release a notice is + generated and the password is cleared. A new password must then + be assigned if the user is to be able to log in with a password. + + + + + + New pg_ctl + + Windows does not have a kill command to send signals to + backends so this capability was added to pg_ctl. + + + + + + Information schema improvements + + + + + + Add + + + + + Detect locale/encoding mismatch in + initdb (Peter) + + + + + + Add + + + + + + + + Data Type and Function Changes + + + + + More complete support for composite types (row types) (Tom) + + + Composite values can be used in many places where only scalar values + worked before. + + + + + + Reject non-rectangular array values as erroneous (Joe) + + + Formerly, array_in would silently build a + surprising result. + + + + + + Overflow in integer arithmetic operations is now detected (Tom) + + + + + + The arithmetic operators associated with the single-byte + "char" data type have been removed. + + + Formerly, the parser would select these operators in many situations + where an unable to select an operator error would be more + appropriate, such as null * null. If you actually want + to do arithmetic on a "char" column, you can cast it to + integer explicitly. + + + + + + Syntax checking of array input values considerably tightened up (Joe) + + + Junk that was previously allowed in odd places with odd results + now causes an ERROR, for example, non-whitespace + after the closing right brace. + + + + + + Empty-string array element values must now be written as + "", rather than writing nothing (Joe) + + + Formerly, both ways of writing an empty-string element value were + allowed, but now a quoted empty string is required. The case where + nothing at all appears will probably be considered to be a NULL + element value in some future release. + + + + + + Array element trailing whitespace is now ignored (Joe) + + + Formerly leading whitespace was ignored, but trailing whitespace + between an element value and the delimiter or right brace was + significant. Now trailing whitespace is also ignored. + + + + + + Emit array values with explicit array bounds when lower bound is not one + (Joe) + + + + + + Accept YYYY-monthname-DD as a date string (Tom) + + + + + + Make netmask and hostmask functions + return maximum-length mask length (Tom) + + + + + + Change factorial function to return numeric (Gavin) + + + Returning numeric allows the factorial function to + work for a wider range of input values. + + + + + + to_char/to_date() date conversion + improvements (Kurt Roeckx, Fabien Coelho) + + + + + + Make length() disregard trailing spaces in + CHAR(n) (Gavin) + + + This change was made to improve consistency: trailing spaces are + semantically insignificant in CHAR(n) data, so they + should not be counted by length(). + + + + + + Warn about empty string being passed to + OID/float4/float8 data types (Neil) + + + 8.1 will throw an error instead. + + + + + + Allow leading or trailing whitespace in + int2/int4/int8/float4/float8 + input routines + (Neil) + + + + + + Better support for IEEE Infinity and NaN + values in float4/float8 (Neil) + + + These should now work on all platforms that support IEEE-compliant + floating point arithmetic. + + + + + + Add + + + + + Fix to_char for 1 BC + (previously it returned 1 AD) (Bruce) + + + + + + Fix date_part(year) for BC dates (previously it + returned one less than the correct year) (Bruce) + + + + + + Fix date_part() to return the proper millennium and + century (Fabien Coelho) + + + In previous versions, the century and millennium results had a wrong + number and started in the wrong year, as compared to standard + reckoning of such things. + + + + + + Add ceiling() as an alias for ceil(), + and power() as an alias for pow() for + standards compliance (Neil) + + + + + + Change ln(), log(), + power(), and sqrt() to emit the correct + SQLSTATE error codes for certain error conditions, as + specified by SQL:2003 (Neil) + + + + + + Add width_bucket() function as defined by SQL:2003 (Neil) + + + + + + Add generate_series() functions to simplify working + with numeric sets (Joe) + + + + + + Fix upper/lower/initcap() functions to work with + multibyte encodings (Tom) + + + + + + Add boolean and bitwise integer + + + + + New session information functions to return network addresses for client + and server (Sean Chittenden) + + + + + + Add function to determine the area of a closed path (Sean Chittenden) + + + + + + Add function to send cancel request to other backends (Magnus) + + + + + + Add interval plus datetime operators (Tom) + + + The reverse ordering, datetime plus interval, + was already supported, but both are required by the SQL standard. + + + + + + Casting an integer to BIT(N) selects the rightmost N bits + of the integer + (Tom) + + + In prior releases, the leftmost N bits were selected, but this was + deemed unhelpful, not to mention inconsistent with casting from bit + to int. + + + + + + Require CIDR values to have all non-masked bits be zero + (Kevin Brintnall) + + + + + + + + + Server-Side Language Changes + + + + + In READ COMMITTED serialization mode, volatile functions + now see the results of concurrent transactions committed up to the + beginning of each statement within the function, rather than up to the + beginning of the interactive command that called the function. + + + + + + Functions declared STABLE or IMMUTABLE always + use the snapshot of the calling query, and therefore do not see the + effects of actions taken after the calling query starts, whether in + their own transaction or other transactions. Such a function must be + read-only, too, meaning that it cannot use any SQL commands other than + SELECT. There is a considerable performance gain from + declaring a function STABLE or IMMUTABLE + rather than VOLATILE. + + + + + + Non-deferred + + + + + Allow function parameters to be declared with names (Dennis Bjorklund) + + + This allows better documentation of functions. Whether the names + actually do anything depends on the specific function language + being used. + + + + + + Allow PL/pgSQL parameter names to be referenced in the function (Dennis Bjorklund) + + + This basically creates an automatic alias for each named parameter. + + + + + + Do minimal syntax checking of PL/pgSQL functions at creation time (Tom) + + + This allows us to catch simple syntax errors sooner. + + + + + + More support for composite types (row and record variables) in PL/pgSQL + + + For example, it now works to pass a rowtype variable to another function + as a single variable. + + + + + + Default values for PL/pgSQL variables can now reference previously + declared variables + + + + + + Improve parsing of PL/pgSQL FOR loops (Tom) + + + Parsing is now driven by presence of ".." rather than + data type of + + + + + Major overhaul of PL/Perl server-side language (Command Prompt, Andrew Dunstan) + + + + + + In PL/Tcl, SPI commands are now run in subtransactions. If an error + occurs, the subtransaction is cleaned up and the error is reported + as an ordinary Tcl error, which can be trapped with catch. + Formerly, it was not possible to catch such errors. + + + + + + Accept ELSEIF in PL/pgSQL (Neil) + + + Previously PL/pgSQL only allowed ELSIF, but many people + are accustomed to spelling this keyword ELSEIF. + + + + + + + + + <application>psql</> Changes + + + + + Improve psql information display about database + objects (Christopher) + + + + + + Allow psql to display group membership in + \du and \dg (Markus Bertheau) + + + + + + Prevent psql \dn from showing + temporary schemas (Bruce) + + + + + + Allow psql to handle tilde user expansion for file + names (Zach Irmen) + + + + + + Allow psql to display fancy prompts, including + color, via readline (Reece Hart, Chet Ramey) + + + + + + Make psql \copy match COPY command syntax + fully (Tom) + + + + + + Show the location of syntax errors (Fabien Coelho, Tom) + + + + + + Add CLUSTER information to psql + \d display + (Bruce) + + + + + + Change psql \copy stdin/stdout to read + from command input/output (Bruce) + + + + + + Add + + + + + Add global psql configuration file, psqlrc.sample + (Bruce) + + + This allows a central file where global psql startup commands can + be stored. + + + + + + Have psql \d+ indicate if the table + has an OID column (Neil) + + + + + + On Windows, use binary mode in psql when reading files so control-Z + is not seen as end-of-file + + + + + + Have \dn+ show permissions and description for schemas (Dennis + Bjorklund) + + + + + + Improve tab completion support (Stefan Kaltenbrunn, Greg Sabino Mullane) + + + + + + Allow boolean settings to be set using upper or lower case (Michael Paesold) + + + + + + + + + <application>pg_dump</> Changes + + + + + Use dependency information to improve the reliability of + pg_dump (Tom) + + + This should solve the longstanding problems with related objects + sometimes being dumped in the wrong order. + + + + + + Have pg_dump output objects in alphabetical order if possible (Tom) + + + This should make it easier to identify changes between + dump files. + + + + + + Allow pg_restore to ignore some SQL errors (Fabien Coelho) + + + This makes pg_restore's behavior similar to the + results of feeding a pg_dump output script to + psql. In most cases, ignoring errors and plowing + ahead is the most useful thing to do. Also added was a pg_restore + option to give the old behavior of exiting on an error. + + + + + + pg_restore + + + + + New begin/end markers in pg_dump text output (Bruce) + + + + + + Add start/stop times for + pg_dump/pg_dumpall in verbose mode + (Bruce) + + + + + + Allow most pg_dump options in + pg_dumpall (Christopher) + + + + + + Have pg_dump use ALTER OWNER rather + than SET SESSION AUTHORIZATION by default + (Christopher) + + + + + + + + + libpq Changes + + + + + Make libpq's + + + + + Add PQmbdsplen() which returns the display length + of a character (Tatsuo) + + + + + + Add thread locking to SSL and + Kerberos connections (Manfred Spraul) + + + + + + Allow PQoidValue(), PQcmdTuples(), and + PQoidStatus() to work on EXECUTE + commands (Neil) + + + + + + Add PQserverVersion() to provide more convenient + access to the server version number (Greg Sabino Mullane) + + + + + + Add PQprepare/PQsendPrepared() functions to support + preparing statements without necessarily specifying the data types + of their parameters (Abhijit Menon-Sen) + + + + + + Many ECPG improvements, including SET DESCRIPTOR (Michael) + + + + + + + + + Source Code Changes + + + + + Allow the database server to run natively on Windows (Claudio, Magnus, Andrew) + + + + + + Shell script commands converted to C versions for Windows support (Andrew) + + + + + + Create an extension makefile framework (Fabien Coelho, Peter) + + + This simplifies the task of building extensions outside the original + source tree. + + + + + + Support relocatable installations (Bruce) + + + Directory paths for installed files (such as the + /share directory) are now computed relative to the + actual location of the executables, so that an installation tree + can be moved to another place without reconfiguring and + rebuilding. + + + + + + Use + + + + + Add + + + + + Upgrade to DocBook V4.2 SGML (Peter) + + + + + + New PostgreSQL CVS tag (Marc) + + + This was done to make it easier for organizations to manage their + own copies of the PostgreSQL + CVS repository. File version stamps from the master + repository will not get munged by checking into or out of a copied + repository. + + + + + + Clarify locking code (Manfred Koizar) + + + + + + Buffer manager cleanup (Neil) + + + + + + Decouple platform tests from CPU spinlock code (Bruce, Tom) + + + + + + Add inlined test-and-set code on PA-RISC for gcc + (ViSolve, Tom) + + + + + + Improve i386 spinlock code (Manfred Spraul) + + + + + + Clean up spinlock assembly code to avoid warnings from newer + gcc releases (Tom) + + + + + + Remove JDBC from source tree; now a separate project + + + + + + Remove the libpgtcl client interface; now a separate project + + + + + + More accurately estimate memory and file descriptor usage (Tom) + + + + + + Improvements to the Mac OS X startup scripts (Ray A.) + + + + + + New fsync() test program (Bruce) + + + + + + Major documentation improvements (Neil, Peter) + + + + + + Remove pg_encoding; not needed + anymore + + + + + + Remove pg_id; not needed anymore + + + + + + Remove initlocation; not needed + anymore + + + + + + Auto-detect thread flags (no more manual testing) (Bruce) + + + + + + Use Olson's public domain timezone library (Magnus) + + + + + + With threading enabled, use thread flags on Unixware for + backend executables too (Bruce) + + + Unixware cannot mix threaded and non-threaded object files in the + same executable, so everything must be compiled as threaded. + + + + + + psql now uses a flex-generated + lexical analyzer to process command strings + + + + + + Reimplement the linked list data structure used throughout the + backend (Neil) + + + This improves performance by allowing list append and length + operations to be more efficient. + + + + + + Allow dynamically loaded modules to create their own server configuration + parameters (Thomas Hallgren) + + + + + + New Brazilian version of FAQ (Euler Taveira de Oliveira) + + + + + + Add French FAQ (Guillaume Lelarge) + + + + + + New pgevent for Windows logging + + + + + + Make libpq and ECPG build as proper shared libraries on OS X (Tom) + + + + + + + + + Contrib Changes + + + + + Overhaul of contrib/dblink (Joe) + + + + + + contrib/dbmirror improvements (Steven Singer) + + + + + + New contrib/xml2 (John Gray, Torchbox) + + + + + + Updated contrib/mysql + + + + + + New version of contrib/btree_gist (Teodor) + + + + + + New contrib/trgm, trigram matching for + PostgreSQL (Teodor) + + + + + + Many contrib/tsearch2 improvements (Teodor) + + + + + + Add double metaphone to contrib/fuzzystrmatch (Andrew) + + + + + + Allow contrib/pg_autovacuum to run as a Windows service (Dave Page) + + + + + + Add functions to contrib/dbsize (Andreas Pflug) + + + + + + Removed contrib/pg_logger: obsoleted by integrated logging + subprocess + + + + + + Removed contrib/rserv: obsoleted by various separate projects + + + + + + + + + + + Release 7.4.9 - - - Allow contrib/pg_autovacuum to run as a Windows service (Dave Page) - - + + Release date + 2005-10-04 + - - - Add functions to contrib/dbsize (Andreas Pflug) - - + + This release contains a variety of fixes from 7.4.8. + - - - Removed contrib/pg_logger: obsoleted by integrated logging - subprocess - - + + Migration to version 7.4.9 - - - Removed contrib/rserv: obsoleted by various separate projects - - + + A dump/restore is not required for those running 7.4.X. However, + if you are upgrading from a version earlier than 7.4.8, see the release + notes for 7.4.8. + + - - + + Changes - - + +Fix error that allowed VACUUM to remove +ctid chains too soon, and add more checking in code that follows +ctid links +This fixes a long-standing problem that could cause crashes in very rare +circumstances. +Fix CHAR() to properly pad spaces to the specified +length when using a multiple-byte character set (Yoshiyuki Asaba) +In prior releases, the padding of CHAR() was incorrect +because it only padded to the specified number of bytes without +considering how many characters were stored. +Fix planning problem with outer-join ON clauses that reference +only the inner-side relation +Further fixes for x FULL JOIN y ON true corner +cases +Make array_in and array_recv more +paranoid about validating their OID parameter +Fix missing rows in queries like UPDATE a=... WHERE +a... with GiST index on column a +Improve robustness of datetime parsing +Improve checking for partially-written WAL +pages +Improve robustness of signal handling when SSL is +enabled +Don't try to open more than max_files_per_process +files during postmaster startup +Various memory leakage fixes +Various portability improvements +Fix PL/PgSQL to handle var := var correctly when +the variable is of pass-by-reference type +Update contrib/tsearch2 to use current Snowball +code + + + + Release 7.4.8 @@ -2869,8 +3022,8 @@ holder of the lock released it within a very narrow window. ALTER TABLE SET WITHOUT OIDS - - + + Release 7.4.7 @@ -2927,8 +3080,8 @@ datestyles GMT - - + + Release 7.4.6 @@ -2997,8 +3150,8 @@ This could arise in cases such as CLUSTER after ALTER TABLE DROP COLUMN. ECPG prepare statement - - + + Release 7.4.5 @@ -3033,8 +3186,8 @@ still worth a re-release. The bug does not exist in pre-7.4 releases. - - + + Release 7.4.4 @@ -3083,8 +3236,8 @@ aggregate plan Translation updates (various contributors) - - + + Release 7.4.3 @@ -3139,8 +3292,8 @@ names from outer query levels. Numerous translation updates (various contributors) - - + + Release 7.4.2 @@ -3280,8 +3433,8 @@ inconveniences associated with the i/I problem. Various JDBC fixes - - + + Release 7.4.1 @@ -3408,424 +3561,426 @@ DROP SCHEMA information_schema CASCADE; Major changes in this release: + - - - - IN / NOT IN subqueries are - now much more efficient - - - - - In previous releases, IN/NOT - IN subqueries were joined to the upper query by - sequentially scanning the subquery looking for a match. The - 7.4 code uses the same sophisticated techniques used by - ordinary joins and so is much faster. An - IN will now usually be as fast as or faster - than an equivalent EXISTS subquery; this - reverses the conventional wisdom that applied to previous - releases. - - - - - - - Improved GROUP BY processing by using hash buckets - - - - - In previous releases, rows to be grouped had to be sorted - first. The 7.4 code can do GROUP BY - without sorting, by accumulating results into a hash table - with one entry per group. It will still use the sort - technique, however, if the hash table is estimated to be too - large to fit in sort_mem. - - - - - - - New multikey hash join capability - - - - - In previous releases, hash joins could only occur on single - keys. This release allows multicolumn hash joins. - - - - - - - Queries using the explicit JOIN syntax are - now better optimized - - - - - Prior releases evaluated queries using the explicit - JOIN syntax only in the order implied by - the syntax. 7.4 allows full optimization of these queries, - meaning the optimizer considers all possible join orderings - and chooses the most efficient. Outer joins, however, must - still follow the declared ordering. - - - - - - - Faster and more powerful regular expression code - - - - - The entire regular expression module has been replaced with a - new version by Henry Spencer, originally written for Tcl. The - code greatly improves performance and supports several flavors - of regular expressions. - - - - - - - Function-inlining for simple SQL functions - - - - - Simple SQL functions can now be inlined by including their SQL - in the main query. This improves performance by eliminating - per-call overhead. That means simple SQL functions now - behave like macros. - - - - - - - Full support for IPv6 connections and IPv6 address data types - - - - - Previous releases allowed only IPv4 connections, and the IP - data types only supported IPv4 addresses. This release adds - full IPv6 support in both of these areas. - - - - - - - Major improvements in SSL performance and reliability - - - - - Several people very familiar with the SSL API have overhauled - our SSL code to improve SSL key negotiation and error - recovery. - - - - - - - Make free space map efficiently reuse empty index pages, - and other free space management improvements - - - - - In previous releases, B-tree index pages that were left empty - because of deleted rows could only be reused by rows with - index values similar to the rows originally indexed on that - page. In 7.4, VACUUM records empty index - pages and allows them to be reused for any future index rows. - - - - - - - SQL-standard information schema - - - - - The information schema provides a standardized and stable way - to access information about the schema objects defined in a - database. - - - - - - - Cursors conform more closely to the SQL standard - - - - - The commands FETCH and - MOVE have been overhauled to conform more - closely to the SQL standard. - - - - - - - Cursors can exist outside transactions - - - - - These cursors are also called holdable cursors. - - - - - - - New client-to-server protocol - - - - - The new protocol adds error codes, more status information, - faster startup, better support for binary data transmission, - parameter values separated from SQL commands, prepared - statements available at the protocol level, and cleaner - recovery from COPY failures. The older - protocol is still supported by both server and clients. - - - - - - - libpq and - ECPG applications are now fully - thread-safe - - - - - While previous libpq releases - already supported threads, this release improves thread safety - by fixing some non-thread-safe code that was used during - database connection startup. The configure - option must be used to - enable this feature. - - - - - - - New version of full-text indexing - - - - - A new full-text indexing suite is available in - contrib/tsearch2. - - - - - - - New autovacuum tool - + + + + IN / NOT IN subqueries are + now much more efficient + - - - The new autovacuum tool in - contrib/autovacuum monitors the database - statistics tables for - INSERT/UPDATE/DELETE - activity and automatically vacuums tables when needed. - - - + + + In previous releases, IN/NOT + IN subqueries were joined to the upper query by + sequentially scanning the subquery looking for a match. The + 7.4 code uses the same sophisticated techniques used by + ordinary joins and so is much faster. An + IN will now usually be as fast as or faster + than an equivalent EXISTS subquery; this + reverses the conventional wisdom that applied to previous + releases. + + + - - - Array handling has been improved and moved into the server core - + + + Improved GROUP BY processing by using hash buckets + - - - Many array limitations have been removed, and arrays behave - more like fully-supported data types. - - - - - - + + + In previous releases, rows to be grouped had to be sorted + first. The 7.4 code can do GROUP BY + without sorting, by accumulating results into a hash table + with one entry per group. It will still use the sort + technique, however, if the hash table is estimated to be too + large to fit in sort_mem. + + + - - Migration to version 7.4 - - - A dump/restore using pg_dump is - required for those wishing to migrate data from any previous - release. - - - - Observe the following incompatibilities: + + + New multikey hash join capability + + + + + In previous releases, hash joins could only occur on single + keys. This release allows multicolumn hash joins. + + + + + + + Queries using the explicit JOIN syntax are + now better optimized + - - The server-side autocommit setting was removed and - reimplemented in client applications and languages. - Server-side autocommit was causing too many problems with - languages and applications that wanted to control their own - autocommit behavior, so autocommit was removed from the server - and added to individual client APIs as appropriate. + Prior releases evaluated queries using the explicit + JOIN syntax only in the order implied by + the syntax. 7.4 allows full optimization of these queries, + meaning the optimizer considers all possible join orderings + and chooses the most efficient. Outer joins, however, must + still follow the declared ordering. + + + + + Faster and more powerful regular expression code + - Error message wording has changed substantially in this - release. Significant effort was invested to make the messages - more consistent and user-oriented. If your applications try to - detect different error conditions by parsing the error message, - you are strongly encouraged to use the new error code facility instead. + The entire regular expression module has been replaced with a + new version by Henry Spencer, originally written for Tcl. The + code greatly improves performance and supports several flavors + of regular expressions. + + + + + Function-inlining for simple SQL functions + - Inner joins using the explicit JOIN syntax - may behave differently because they are now better - optimized. + Simple SQL functions can now be inlined by including their SQL + in the main query. This improves performance by eliminating + per-call overhead. That means simple SQL functions now + behave like macros. + + + + + Full support for IPv6 connections and IPv6 address data types + - A number of server configuration parameters have been renamed - for clarity, primarily those related to - logging. + Previous releases allowed only IPv4 connections, and the IP + data types only supported IPv4 addresses. This release adds + full IPv6 support in both of these areas. + + + + + Major improvements in SSL performance and reliability + - FETCH 0 or MOVE 0 now - does nothing. In prior releases, FETCH 0 - would fetch all remaining rows, and MOVE 0 - would move to the end of the cursor. + Several people very familiar with the SSL API have overhauled + our SSL code to improve SSL key negotiation and error + recovery. - + + + + + Make free space map efficiently reuse empty index pages, + and other free space management improvements + + - FETCH and MOVE now return - the actual number of rows fetched/moved, or zero if at the - beginning/end of the cursor. Prior releases would return the - row count passed to the command, not the number of rows - actually fetched or moved. + In previous releases, B-tree index pages that were left empty + because of deleted rows could only be reused by rows with + index values similar to the rows originally indexed on that + page. In 7.4, VACUUM records empty index + pages and allows them to be reused for any future index rows. + + + + + SQL-standard information schema + - COPY now can process files that use - carriage-return or carriage-return/line-feed end-of-line - sequences. Literal carriage-returns and line-feeds are no - longer accepted in data values; use \r and - \n instead. + The information schema provides a standardized and stable way + to access information about the schema objects defined in a + database. + + + + + Cursors conform more closely to the SQL standard + - Trailing spaces are now trimmed when converting from type - char(n) to - varchar(n) or text. - This is what most people always expected to happen anyway. + The commands FETCH and + MOVE have been overhauled to conform more + closely to the SQL standard. + + + + + Cursors can exist outside transactions + - The data type float(p) now - measures p in binary digits, not decimal - digits. The new behavior follows the SQL standard. + These cursors are also called holdable cursors. + + + + + New client-to-server protocol + - Ambiguous date values now must match the ordering specified by - the datestyle setting. In prior releases, a - date specification of 10/20/03 was interpreted as a - date in October even if datestyle specified that - the day should be first. 7.4 will throw an error if a date - specification is invalid for the current setting of - datestyle. + The new protocol adds error codes, more status information, + faster startup, better support for binary data transmission, + parameter values separated from SQL commands, prepared + statements available at the protocol level, and cleaner + recovery from COPY failures. The older + protocol is still supported by both server and clients. + + + + + libpq and + ECPG applications are now fully + thread-safe + - The functions oidrand, - oidsrand, and - userfntest have been removed. These - functions were determined to be no longer useful. + While previous libpq releases + already supported threads, this release improves thread safety + by fixing some non-thread-safe code that was used during + database connection startup. The configure + option must be used to + enable this feature. + + + + + New version of full-text indexing + - String literals specifying time-varying date/time values, such - as 'now' or 'today' will - no longer work as expected in column default expressions; they - now cause the time of the table creation to be the default, not - the time of the insertion. Functions such as - now(), current_timestamp, or - current_date should be used instead. + A new full-text indexing suite is available in + contrib/tsearch2. + + + + + + New autovacuum tool + + - In previous releases, there was special code so that strings - such as 'now' were interpreted at - INSERT time and not at table creation time, but - this work around didn't cover all cases. Release 7.4 now - requires that defaults be defined properly using functions such - as now() or current_timestamp. These - will work in all situations. + The new autovacuum tool in + contrib/autovacuum monitors the database + statistics tables for + INSERT/UPDATE/DELETE + activity and automatically vacuums tables when needed. + + + + + Array handling has been improved and moved into the server core + - The dollar sign ($) is no longer allowed in - operator names. It can instead be a non-first character in - identifiers. This was done to improve compatibility with other - database systems, and to avoid syntax problems when parameter - placeholders ($n) are written - adjacent to operators. + Many array limitations have been removed, and arrays behave + more like fully-supported data types. - + + + + + + + Migration to version 7.4 + + + A dump/restore using pg_dump is + required for those wishing to migrate data from any previous + release. + + + + Observe the following incompatibilities: + + + + + The server-side autocommit setting was removed and + reimplemented in client applications and languages. + Server-side autocommit was causing too many problems with + languages and applications that wanted to control their own + autocommit behavior, so autocommit was removed from the server + and added to individual client APIs as appropriate. + + + + + + Error message wording has changed substantially in this + release. Significant effort was invested to make the messages + more consistent and user-oriented. If your applications try to + detect different error conditions by parsing the error message, + you are strongly encouraged to use the new error code facility instead. + + + + + + Inner joins using the explicit JOIN syntax + may behave differently because they are now better + optimized. + + + + + + A number of server configuration parameters have been renamed + for clarity, primarily those related to + logging. + + + + + + FETCH 0 or MOVE 0 now + does nothing. In prior releases, FETCH 0 + would fetch all remaining rows, and MOVE 0 + would move to the end of the cursor. + + + + + + FETCH and MOVE now return + the actual number of rows fetched/moved, or zero if at the + beginning/end of the cursor. Prior releases would return the + row count passed to the command, not the number of rows + actually fetched or moved. + + + + + + COPY now can process files that use + carriage-return or carriage-return/line-feed end-of-line + sequences. Literal carriage-returns and line-feeds are no + longer accepted in data values; use \r and + \n instead. + + + + + + Trailing spaces are now trimmed when converting from type + char(n) to + varchar(n) or text. + This is what most people always expected to happen anyway. + + + + + + The data type float(p) now + measures p in binary digits, not decimal + digits. The new behavior follows the SQL standard. + + + + + + Ambiguous date values now must match the ordering specified by + the datestyle setting. In prior releases, a + date specification of 10/20/03 was interpreted as a + date in October even if datestyle specified that + the day should be first. 7.4 will throw an error if a date + specification is invalid for the current setting of + datestyle. + + + + + + The functions oidrand, + oidsrand, and + userfntest have been removed. These + functions were determined to be no longer useful. + + + + + + String literals specifying time-varying date/time values, such + as 'now' or 'today' will + no longer work as expected in column default expressions; they + now cause the time of the table creation to be the default, not + the time of the insertion. Functions such as + now(), current_timestamp, or + current_date should be used instead. + + + + In previous releases, there was special code so that strings + such as 'now' were interpreted at + INSERT time and not at table creation time, but + this work around didn't cover all cases. Release 7.4 now + requires that defaults be defined properly using functions such + as now() or current_timestamp. These + will work in all situations. + + + + + + The dollar sign ($) is no longer allowed in + operator names. It can instead be a non-first character in + identifiers. This was done to improve compatibility with other + database systems, and to avoid syntax problems when parameter + placeholders ($n) are written + adjacent to operators. + + + + @@ -5252,6 +5407,57 @@ DROP SCHEMA information_schema CASCADE; + + + Release 7.3.11 + + + Release date + 2005-10-04 + + + + This release contains a variety of fixes from 7.3.10. + + + + Migration to version 7.3.11 + + + A dump/restore is not required for those running 7.3.X. However, + if you are upgrading from a version earlier than 7.3.10, see the release + notes for 7.3.10. + + + + + Changes + + +Fix error that allowed VACUUM to remove +ctid chains too soon, and add more checking in code that follows +ctid links +This fixes a long-standing problem that could cause crashes in very rare +circumstances. +Fix CHAR() to properly pad spaces to the specified +length when using a multiple-byte character set (Yoshiyuki Asaba) +In prior releases, the padding of CHAR() was incorrect +because it only padded to the specified number of bytes without +considering how many characters were stored. +Fix missing rows in queries like UPDATE a=... WHERE +a... with GiST index on column a +Improve checking for partially-written WAL +pages +Improve robustness of signal handling when SSL is +enabled +Various memory leakage fixes +Various portability improvements +Fix PL/PgSQL to handle var := var correctly when +the variable is of pass-by-reference type + + + + Release 7.3.10 @@ -5857,290 +6063,289 @@ operations on bytea columns (Joe) Release date - 2002-12-18 - - - - This release contains a variety of fixes for version 7.3. - - - - - Migration to version 7.3.1 - - - A dump/restore is not required for those - running version 7.3. However, it should be noted that the main - PostgreSQL interface library, libpq, - has a new major version number for this release, which may require - recompilation of client code in certain cases. - - - - - Changes - - -Fix a core dump of COPY TO when client/server encodings don't match (Tom) -Allow pg_dump to work with pre-7.2 servers (Philip) -contrib/adddepend fixes (Tom) -Fix problem with deletion of per-user/per-database config settings (Tom) -contrib/vacuumlo fix (Tom) -Allow 'password' encryption even when pg_shadow contains MD5 passwords (Bruce) -contrib/dbmirror fix (Steven Singer) -Optimizer fixes (Tom) -contrib/tsearch fixes (Teodor Sigaev, Magnus) -Allow locale names to be mixed case (Nicolai Tufar) -Increment libpq library's major version number (Bruce) -pg_hba.conf error reporting fixes (Bruce, Neil) -Add SCO Openserver 5.0.4 as a supported platform (Bruce) -Prevent EXPLAIN from crashing server (Tom) -SSL fixes (Nathan Mueller) -Prevent composite column creation via ALTER TABLE (Tom) - - - - - - - Release 7.3 - - - Release date - 2002-11-27 - - - - Overview - - - Major changes in this release: - - - - Schemas - - - Schemas allow users to create objects in separate namespaces, - so two people or applications can have tables with the same - name. There is also a public schema for shared tables. - Table/index creation can be restricted by removing privileges - on the public schema. - - - - - - Drop Column - - - PostgreSQL now supports the - ALTER TABLE ... DROP COLUMN functionality. - - - - - - Table Functions - - - Functions returning multiple rows and/or multiple columns are - now much easier to use than before. You can call such a - table function in the SELECT - FROM clause, treating its output like a - table. Also, PL/pgSQL functions can - now return sets. - - - - - - Prepared Queries - - - PostgreSQL now supports prepared - queries, for improved performance. - - - - - - Dependency Tracking - - - PostgreSQL now records object - dependencies, which allows improvements in many areas. - DROP statements now take either - CASCADE or RESTRICT to control whether - dependent objects are also dropped. - - - - - - Privileges - - - Functions and procedural languages now have privileges, and - functions can be defined to run with the privileges of their - creator. - - - - - - Internationalization - - - Both multibyte and locale support are now always enabled. - - - + 2002-12-18 + - - Logging - - - A variety of logging options have been enhanced. - - - + + This release contains a variety of fixes for version 7.3. + - - Interfaces - - - A large number of interfaces have been moved to http://gborg.postgresql.org - where they can be developed and released independently. - - - - - Functions/Identifiers - - - By default, functions can now take up to 32 parameters, and - identifiers can be up to 63 bytes long. Also, OPAQUE - is now deprecated: there are specific pseudo-datatypes - to represent each of the former meanings of OPAQUE - in function argument and result types. - - - + + Migration to version 7.3.1 - + + A dump/restore is not required for those + running version 7.3. However, it should be noted that the main + PostgreSQL interface library, libpq, + has a new major version number for this release, which may require + recompilation of client code in certain cases. - Migration to version 7.3 + Changes - - A dump/restore using pg_dump is required for those - wishing to migrate data from any previous release. If your - application examines the system catalogs, additional changes will - be required due to the introduction of schemas in 7.3; for more - information, see: . - + +Fix a core dump of COPY TO when client/server encodings don't match (Tom) +Allow pg_dump to work with pre-7.2 servers (Philip) +contrib/adddepend fixes (Tom) +Fix problem with deletion of per-user/per-database config settings (Tom) +contrib/vacuumlo fix (Tom) +Allow 'password' encryption even when pg_shadow contains MD5 passwords (Bruce) +contrib/dbmirror fix (Steven Singer) +Optimizer fixes (Tom) +contrib/tsearch fixes (Teodor Sigaev, Magnus) +Allow locale names to be mixed case (Nicolai Tufar) +Increment libpq library's major version number (Bruce) +pg_hba.conf error reporting fixes (Bruce, Neil) +Add SCO Openserver 5.0.4 as a supported platform (Bruce) +Prevent EXPLAIN from crashing server (Tom) +SSL fixes (Nathan Mueller) +Prevent composite column creation via ALTER TABLE (Tom) + + + + + + + Release 7.3 + + + Release date + 2002-11-27 + + + + Overview - Observe the following incompatibilities: + Major changes in this release: + - + + + Schemas - Pre-6.3 clients are no longer supported. + Schemas allow users to create objects in separate namespaces, + so two people or applications can have tables with the same + name. There is also a public schema for shared tables. + Table/index creation can be restricted by removing privileges + on the public schema. + + + Drop Column - pg_hba.conf now has a column for the user - name and additional features. Existing files need to be - adjusted. + PostgreSQL now supports the + ALTER TABLE ... DROP COLUMN functionality. + + + Table Functions - Several postgresql.conf logging parameters - have been renamed. + Functions returning multiple rows and/or multiple columns are + now much easier to use than before. You can call such a + table function in the SELECT + FROM clause, treating its output like a + table. Also, PL/pgSQL functions can + now return sets. + + + Prepared Queries - LIMIT #,# has been disabled; use - LIMIT # OFFSET #. + PostgreSQL now supports prepared + queries, for improved performance. + + + Dependency Tracking - INSERT statements with column lists must - specify a value for each specified column. For example, - INSERT INTO tab (col1, col2) VALUES ('val1') - is now invalid. It's still allowed to supply fewer columns than - expected if the INSERT does not have a column list. + PostgreSQL now records object + dependencies, which allows improvements in many areas. + DROP statements now take either + CASCADE or RESTRICT to control whether + dependent objects are also dropped. + + + Privileges - serial columns are no longer automatically - UNIQUE; thus, an index will not automatically be - created. + Functions and procedural languages now have privileges, and + functions can be defined to run with the privileges of their + creator. + + + Internationalization - A SET command inside an aborted transaction - is now rolled back. + Both multibyte and locale support are now always enabled. + + + Logging - COPY no longer considers missing trailing - columns to be null. All columns need to be specified. - (However, one may achieve a similar effect by specifying a - column list in the COPY command.) + A variety of logging options have been enhanced. + + + Interfaces - The data type timestamp is now equivalent to - timestamp without time zone, instead of - timestamp with time zone. + A large number of interfaces have been moved to http://gborg.postgresql.org + where they can be developed and released independently. + + + Functions/Identifiers - Pre-7.3 databases loaded into 7.3 will not have the new object - dependencies for serial columns, unique - constraints, and foreign keys. See the directory - contrib/adddepend/ for a detailed - description and a script that will add such dependencies. + By default, functions can now take up to 32 parameters, and + identifiers can be up to 63 bytes long. Also, OPAQUE + is now deprecated: there are specific pseudo-datatypes + to represent each of the former meanings of OPAQUE + in function argument and result types. + - - - An empty string ('') is no longer allowed as - the input into an integer field. Formerly, it was silently - interpreted as 0. - - + + - + + Migration to version 7.3 + + + A dump/restore using pg_dump is required for those + wishing to migrate data from any previous release. If your + application examines the system catalogs, additional changes will + be required due to the introduction of schemas in 7.3; for more + information, see: . + + + + Observe the following incompatibilities: + + + + Pre-6.3 clients are no longer supported. + + + + + + pg_hba.conf now has a column for the user + name and additional features. Existing files need to be + adjusted. + + + + + + Several postgresql.conf logging parameters + have been renamed. + + + + + + LIMIT #,# has been disabled; use + LIMIT # OFFSET #. + + + + + + INSERT statements with column lists must + specify a value for each specified column. For example, + INSERT INTO tab (col1, col2) VALUES ('val1') + is now invalid. It's still allowed to supply fewer columns than + expected if the INSERT does not have a column list. + + + + + + serial columns are no longer automatically + UNIQUE; thus, an index will not automatically be + created. + + + + + + A SET command inside an aborted transaction + is now rolled back. + + + + + + COPY no longer considers missing trailing + columns to be null. All columns need to be specified. + (However, one may achieve a similar effect by specifying a + column list in the COPY command.) + + + + + + The data type timestamp is now equivalent to + timestamp without time zone, instead of + timestamp with time zone. + + + + + + Pre-7.3 databases loaded into 7.3 will not have the new object + dependencies for serial columns, unique + constraints, and foreign keys. See the directory + contrib/adddepend/ for a detailed + description and a script that will add such dependencies. + + + + + + An empty string ('') is no longer allowed as + the input into an integer field. Formerly, it was silently + interpreted as 0. + + + + @@ -6865,196 +7070,198 @@ since PostgreSQL 7.1. Migration to version 7.2.1 - - - A dump/restore is not required for those - running version 7.2. - - - - - Changes - - -Ensure that sequence counters do not go backwards after a crash (Tom) -Fix pgaccess kanji-conversion key binding (Tatsuo) -Optimizer improvements (Tom) -Cash I/O improvements (Tom) -New Russian FAQ -Compile fix for missing AuthBlockSig (Heiko) -Additional time zones and time zone fixes (Thomas) -Allow psql \connect to handle mixed case database and user names (Tom) -Return proper OID on command completion even with ON INSERT rules (Tom) -Allow COPY FROM to use 8-bit DELIMITERS (Tatsuo) -Fix bug in extract/date_part for milliseconds/microseconds (Tatsuo) -Improve handling of multiple UNIONs with different lengths (Tom) -contrib/btree_gist improvements (Teodor Sigaev) -contrib/tsearch dictionary improvements, see README.tsearch for an additional installation step (Thomas T. Thai, Teodor Sigaev) -Fix for array subscripts handling (Tom) -Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom) - - - - - - - Release 7.2 - - - Release date - 2002-02-04 - - - - Overview - - - This release improves PostgreSQL for use in - high-volume applications. - - - - Major changes in this release: - - - - VACUUM - - - Vacuuming no longer locks tables, thus allowing normal user - access during the vacuum. A new VACUUM FULL - command does old-style vacuum by locking the table and - shrinking the on-disk copy of the table. - - - - - - Transactions - - - There is no longer a problem with installations that exceed - four billion transactions. - - - - - - OIDs - - - OIDs are now optional. Users can now create tables without - OIDs for cases where OID usage is excessive. - - - - - - Optimizer - - - The system now computes histogram column statistics during - ANALYZE, allowing much better optimizer choices. - - - - - - Security - - - A new MD5 encryption option allows more secure storage and - transfer of passwords. A new Unix-domain socket - authentication option is available on Linux and BSD systems. - - - - - - Statistics - - - Administrators can use the new table access statistics module - to get fine-grained information about table and index usage. - - - - - - Internationalization - - - Program and library messages can now be displayed in several - languages. - - - - + + + A dump/restore is not required for those + running version 7.2. - Migration to version 7.2 + Changes + + +Ensure that sequence counters do not go backwards after a crash (Tom) +Fix pgaccess kanji-conversion key binding (Tatsuo) +Optimizer improvements (Tom) +Cash I/O improvements (Tom) +New Russian FAQ +Compile fix for missing AuthBlockSig (Heiko) +Additional time zones and time zone fixes (Thomas) +Allow psql \connect to handle mixed case database and user names (Tom) +Return proper OID on command completion even with ON INSERT rules (Tom) +Allow COPY FROM to use 8-bit DELIMITERS (Tatsuo) +Fix bug in extract/date_part for milliseconds/microseconds (Tatsuo) +Improve handling of multiple UNIONs with different lengths (Tom) +contrib/btree_gist improvements (Teodor Sigaev) +contrib/tsearch dictionary improvements, see README.tsearch for an additional installation step (Thomas T. Thai, Teodor Sigaev) +Fix for array subscripts handling (Tom) +Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom) + + + + + + + Release 7.2 + + + Release date + 2002-02-04 + + + + Overview - A dump/restore using pg_dump is required for - those wishing to migrate data from any previous release. + This release improves PostgreSQL for use in + high-volume applications. - Observe the following incompatibilities: + Major changes in this release: + - + + + VACUUM - The semantics of the VACUUM command have - changed in this release. You may wish to update your - maintenance procedures accordingly. + Vacuuming no longer locks tables, thus allowing normal user + access during the vacuum. A new VACUUM FULL + command does old-style vacuum by locking the table and + shrinking the on-disk copy of the table. + + + Transactions - In this release, comparisons using = NULL - will always return false (or NULL, more precisely). Previous - releases automatically transformed this syntax to IS - NULL. The old behavior can be re-enabled using a - postgresql.conf parameter. + There is no longer a problem with installations that exceed + four billion transactions. + + + OIDs - The pg_hba.conf and pg_ident.conf - configuration is now only reloaded after receiving a - SIGHUP signal, not with each connection. + OIDs are now optional. Users can now create tables without + OIDs for cases where OID usage is excessive. + + + Optimizer - The function octet_length() now returns the uncompressed data length. + The system now computes histogram column statistics during + ANALYZE, allowing much better optimizer choices. + + + Security - The date/time value 'current' is no longer - available. You will need to rewrite your applications. + A new MD5 encryption option allows more secure storage and + transfer of passwords. A new Unix-domain socket + authentication option is available on Linux and BSD systems. + + + Statistics - The timestamp(), time(), - and interval() functions are no longer - available. Instead of timestamp(), use - timestamp 'string' or CAST. + Administrators can use the new table access statistics module + to get fine-grained information about table and index usage. - + + + + Internationalization + + + Program and library messages can now be displayed in several + languages. + + + + + + + + + Migration to version 7.2 + + + A dump/restore using pg_dump is required for + those wishing to migrate data from any previous release. + + + + Observe the following incompatibilities: + + + + The semantics of the VACUUM command have + changed in this release. You may wish to update your + maintenance procedures accordingly. + + + + + + In this release, comparisons using = NULL + will always return false (or NULL, more precisely). Previous + releases automatically transformed this syntax to IS + NULL. The old behavior can be re-enabled using a + postgresql.conf parameter. + + + + + + The pg_hba.conf and pg_ident.conf + configuration is now only reloaded after receiving a + SIGHUP signal, not with each connection. + + + + + + The function octet_length() now returns the uncompressed data length. + + + + + + The date/time value 'current' is no longer + available. You will need to rewrite your applications. + + + + + + The timestamp(), time(), + and interval() functions are no longer + available. Instead of timestamp(), use + timestamp 'string' or CAST. + + + + + The SELECT ... LIMIT #,# syntax will be removed in the next release. You should change your queries to use @@ -7589,83 +7796,83 @@ Python fixes (Darcy) Major changes in this release: + - - - - Write-ahead Log (WAL) - - - + + + + Write-ahead Log (WAL) + + + To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. - - - + + + - - - TOAST - - - - TOAST - Previous releases had a compiled-in row length limit, + + + TOAST + + + + TOAST - Previous releases had a compiled-in row length limit, typically 8k - 32k. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. - - - + + + - - - Outer Joins - - - + + + Outer Joins + + + We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. - - - + + + - - - Function Manager - - - + + + Function Manager + + + The previous C function manager did not handle null values properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. - - - + + + - - - Complex Queries - - - + + + Complex Queries + + + A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. - - - + + + - - + Migration to version 7.1 @@ -8052,62 +8259,63 @@ ecpg changes (Michael) Major changes in this release: + - - - - Foreign Keys - - - - Foreign keys are now implemented, with the exception of PARTIAL MATCH - foreign keys. Many users have been asking for this feature, and we are - pleased to offer it. - - - + + + + Foreign Keys + + + + Foreign keys are now implemented, with the exception of PARTIAL MATCH + foreign keys. Many users have been asking for this feature, and we are + pleased to offer it. + + + - - - Optimizer Overhaul - - - - Continuing on work started a year ago, the optimizer has been - improved, allowing better query plan selection and faster performance - with less memory usage. - - - + + + Optimizer Overhaul + + + + Continuing on work started a year ago, the optimizer has been + improved, allowing better query plan selection and faster performance + with less memory usage. + + + - - - Updated psql - - - - psql, our interactive terminal monitor, has been - updated with a variety of new features. See the psql manual page for details. - - - + + + Updated psql + + + + psql, our interactive terminal monitor, has been + updated with a variety of new features. See the psql manual page for details. + + + - - - Join Syntax - - - - SQL92 join syntax is now supported, though only as - INNER JOIN for this release. JOIN, - NATURAL JOIN, JOIN/USING, - and JOIN/ON are available, as are - column correlation names. - - - - - + + + Join Syntax + + + + SQL92 join syntax is now supported, though only as + INNER JOIN for this release. JOIN, + NATURAL JOIN, JOIN/USING, + and JOIN/ON are available, as are + column correlation names. + + + + + Migration to version 7.0 @@ -8125,54 +8333,53 @@ ecpg changes (Michael) Interface and compatibility issues to consider for the new release include: + - - - - The date/time types datetime and - timespan have been superseded by the - SQL92-defined types timestamp and - interval. Although there has been some effort to - ease the transition by allowing - PostgreSQL to recognize - the deprecated type names and translate them to the new type - names, this mechanism may not be completely transparent to - your existing application. - - - - - - The optimizer has been substantially improved in the area of - query cost estimation. In some cases, this will result in - decreased query times as the optimizer makes a better choice - for the preferred plan. However, in a small number of cases, - usually involving pathological distributions of data, your - query times may go up. If you are dealing with large amounts - of data, you may want to check your queries to verify - performance. - - + + + + The date/time types datetime and + timespan have been superseded by the + SQL92-defined types timestamp and + interval. Although there has been some effort to + ease the transition by allowing + PostgreSQL to recognize + the deprecated type names and translate them to the new type + names, this mechanism may not be completely transparent to + your existing application. + + - - - The JDBC and ODBC - interfaces have been upgraded and extended. - - + + + The optimizer has been substantially improved in the area of + query cost estimation. In some cases, this will result in + decreased query times as the optimizer makes a better choice + for the preferred plan. However, in a small number of cases, + usually involving pathological distributions of data, your + query times may go up. If you are dealing with large amounts + of data, you may want to check your queries to verify + performance. + + - - - The string function CHAR_LENGTH is now a - native function. Previous versions translated this into a call - to LENGTH, which could result in - ambiguity with other types implementing - LENGTH such as the geometric types. - - - - + + + The JDBC and ODBC + interfaces have been upgraded and extended. + + + + + The string function CHAR_LENGTH is now a + native function. Previous versions translated this into a call + to LENGTH, which could result in + ambiguity with other types implementing + LENGTH such as the geometric types. + + + @@ -11226,4 +11433,3 @@ sgml-local-catalogs:("/usr/lib/sgml/catalog") sgml-local-ecat-files:nil End: --> -