+ url="http://pgfoundry.org/projects/pginstaller">
http://pgfoundry.org/projects/pginstaller.
Although tested throughout our release cycle, the Windows port
- does not have the benefit of years of use in production
- environments that PostgreSQL has on Unix platforms and
- therefore should be treated with the same level of caution as
- you would a new product.
+ does not have the benefit of years of use in production
+ environments that
PostgreSQL has on+ Unix platforms and therefore should be treated with the same
+ level of caution as you would a new product.
- Previous releases required the Unix emulation toolkit Cygwin for
- Win32 server support.
PostgreSQL- has always supported clients on Win32.
+
Previous releases required the Unix emulation toolkit+
Cygwin for Win32 server support.+
PostgreSQL has always supported
+ clients on Win32.
- CSV support in COPY
+ Comma-separated-value (CSV) support in COPY
COPY can now read and write
- comma-separated-value (CSV) files. It has the flexibility to
+ comma-separated-value files. It has the flexibility to
interpret non-standard quoting and separation characters too.
- The length() function no longer counts trailing spaces in
- CHAR(n) values.
+ The length() function no longer counts trailing spaces in
+ CHAR(n) values.
- Casting an integer to BIT(N) selects the rightmost N bits of the
+ Casting an integer to BIT(N) selects the rightmost N bits of the
integer, not the leftmost N bits as before.
- UPDATE-ing an element or slice of a NULL array value now produces
+ Updating an element or slice of a NULL array value now produces
a non-NULL array result, namely an array containing
just the assigned-to positions.
- The arithmetic operators associated with the char data typ
e
- have been removed.
+ The arithmetic operators associated with the single-byte
+ "char" data type has been removed.
- The extract() function (also called date_part) now returns the proper
- year for BC dates. It previously returned one less than the current
- year. The function now also returns the proper values for millennium
- and century.
+ The extract() function (also called
+ date_part) now returns the proper year for BC dates.
+ It previously returned one less than the current year. The
+ function now also returns the proper values for millennium and
+ century.
- psql's \copy command now reads or writes the query stdin/stdout, rather
- than psql's stdin/stdout. The previous behavior can be accessed via new
- pstdin/pstdout parameters.
+
psql's \copy command now reads or+ writes to the query's stdin/stdout, rather than
+
psql's stdin/stdout. The previous+ behavior can be accessed via new
+ >
- configure's threading option no longer requires users to run
- tests or edit configuration files; threading options are now detected
- automatically.
+
Configure's threading option no longer requires+ users to run tests or edit configuration files; threading options
+ are now detected automatically.
Syntax checking of array input values has been tightened up
considerably. Junk that was previously allowed in odd places with
- odd results now causes an ERROR. Empty-string element values must
- now be written as "", rather than writing nothing.
- Also changed behavior with respect to whitespace surrounding array
- elements: trailing whitespace is now ignored, for symmetry with leading
- whitespace (which has always been ignored).
+ odd results now causes an ERROR. Empty-string element
+ values must now be written as "", rather than writing nothing.
+ Also changed behavior with respect to whitespace surrounding
+ array elements: trailing whitespace is now ignored, for symmetry
+ with leading whitespace (which has always been ignored).
- In <literal>READ COMMITTED serialization mode, volatile functions
+ In <option>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 <literal>STABLE or >IMMUTABLE always
+ Functions declared <option>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
- Non-deferred AFTER triggers are now fired immediately after completion
- of the triggering query, rather than upon finishing the current
- interactive command. This makes a difference when the triggering query
- occurred within a function: the trigger is invoked before the function
- proceeds to its next operation.
+ Non-deferred
+ after completion of the triggering query, rather than upon
+ finishing the current interactive command. This makes a
+ difference when the triggering query occurred within a function:
+ the trigger is invoked before the function proceeds to its next
+ operation.
- CIDR values now must have their non-masked bits be zero. For example,
- no longer allow 204.248.199.1/31 as a CIDR value.
- Such values should have never been accepted by PostgreSQL and will now be
- rejected.
+ CIDR values now must have their non-masked bits be zero.
+ For example, we no longer allow
+ 204.248.199.1/31 as a CIDR>/> value. Such
+ values should never have been accepted by
+
PostgreSQL and will now be rejected.
The 8.1 release will remove the function
- <literal>to_char(interval)>.
+ <function>to_char(interval)>.
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 WITH OIDS> clause must
+ and earlier are created with OIDs. In the next release,
+ this will not be the case: to create a table
+ that contains OIDs, the
be specified or the default_with_oids
configuration parameter must be enabled. Users are encouraged to
- explicitly specify <literal>WITH OIDS> if their tables
+ explicitly specify <option>WITH OIDS> if their tables
require OIDs for compatibility with future releases of
- Add subprocess to write dirty buffers periodically to reduce checkpoint writes (Jan)
+ Add subprocess to write dirty buffers periodically to reduce
+ checkpoint writes (Jan)
In previous releases, the checkpoint process, which runs every few
disk. This often resulted in a periodic spike in disk usage that
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.
+ 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.
- Improved index usage with OR clauses (Tom)
+ 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.
+ column is part of an OR clause.
The server is now smarter about using partial indexes in queries
- involving complex WHERE clauses.
+ involving complex clauses.
It is now possible to log server messages conveniently without
- relying on either syslog or an external log rotation program.
+ relying on either
syslog or an external log+ rotation program.
- Make quoting of "sameuser", "samegroup", and "all" remove
- special meaning of these terms in pg_hba.conf (Andrew)
+ 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 clearer IPv6 name ::1/128 for
+ localhost in default pg_hba.conf (Andrew)
- Use CIDR format in pg_hba.conf examples (Andrew)
+ Use CIDR format in pg_hba.conf examples (Andrew)
Listen on localhost by default, which eliminates the need for the
- <literal>-i postmaster switch in many scenarios (Andrew)
+ <option>-i postmaster switch in many scenarios (Andrew)
- Listening on localhost (127.0.0.1) opens no new security holes but
- allows configurations like Win32 and JDBC, which do not support
- local sockets, to work without special adjustments.
+ Listening on localhost (127.0.0.1) opens no new
+ security holes but allows configurations like Win32 and JDBC,
+ which do not support local sockets, to work without special
+ adjustments.
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.
+ Parse message with parameters. The parameter values
+ sent at Bind time will be substituted into the
+ execution of the cursor's query.
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
- datatype.)
+ data type.)
Make CASE val WHEN compval1 THEN ... evaluate val only once (Tom)
- CASE no longer evaluates the test expression multiple
+ no longer evaluates the test expression multiple
times. This has benefits when the expression is complex or is
volatile.
- Test HAVING before computing target list of an aggregate query (Tom)
+ Test
+ aggregate query (Tom)
- Fixes improper failure of cases such as SELECT SUM(win)/SUM(lose)
- ... GROUP BY ... HAVING SUM(lose) > 0. This should work but formerly
+ 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.
- Allow LIKE/ILIKE to be used as the operator in row and subselect
- comparisons (Fabien Coelho)
+ Allow
+ in row and subselect comparisons (Fabien Coelho)
- Avoid emitting NATURAL CROSS JOIN in rule listings (Tom)
+ Avoid emitting in rule listings (Tom)
Such a clause makes no logical sense, but in some cases the rule
- Add COMMENT ON casts, conversions, languages, operator classes, and
- large objects (Christopher)
+ 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)
+ control whether tables are created with OIDs by default (Neil)
This allows administrators to default all CREATE
- TABLE commands to create tables without OID columns.
+ TABLE commands to create tables without OID
+ columns.
- Add WITH / WITHOUT OIDS clause to CREATE TABLE
- AS (Neil)
+ Add
+ CREATE TABLE AS (Neil)
- Allow ALTER TABLE DROP COLUMN to drop an OID column
- (ALTER TABLE SET WITHOUT OIDS still works) (Tom)
+ Allow ALTER TABLE DROP COLUMN to drop an OID
+ column (ALTER TABLE SET WITHOUT OIDS still works)
+ (Tom)
- Allow ALTER ... ADD COLUMN with defaults and NOT NULL constraints;
- works per SQL spec (Rod)
+ Allow ALTER ... ADD COLUMN with defaults and
+ works per SQL spec (Rod)
- It is now possible for ADD COLUMN to create a column that is not
- initially filled with NULLs, but with a specified default value.
+ It is now possible for
+ that is not initially filled with NULLs, but with a specified
+ default value.
- Add ALTER COLUMN TYPE to change column's type (Rod)
+ Add ALTER COLUMN TYPE to change column's type (Rod)
- It is now possible to alter a column's datatype without dropping
+ 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
+ Allow multiple ALTER actions in a single ALTER
TABLE command (Rod)
- This is particularly useful for ALTER commands that rewrite the
- table (which include ALTER COLUMN TYPE and ADD COLUMN with a default).
- By grouping ALTER commands together, the table need be
- rewritten only once.
+ This is particularly useful for ALTER commands that
+ rewrite the table (which include
+
+ ALTER commands together, the table need be rewritten
+ only once.
- Allow ALTER TABLE to add serial
+ Allow ALTER TABLE to add SERIAL
columns (Tom)
- Allow temporary object creation to be limited to SECURITY DEFINER
- functions (Sean Chittenden)
+ Allow temporary object creation to be limited to
+ DEFINER functions (Sean Chittenden)
- Add ALTER TABLE ... SET WITHOUT CLUSTER (Christopher)
+ Add (Christopher)
Prior to this release, there was no way to clear an auto-cluster
- Constraint/Index/SERIAL names are now table_column_type with numbers
- appended to guarantee uniqueness within the schema (Tom)
+ 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
- Add pg_get_serial_sequence() to return a serial column's
- sequence name (Christopher)
+ Add pg_get_serial_sequence() to return a
+ SERIAL column's sequence name (Christopher)
- This allows automated scripts to reliabily find the serial
+ This allows automated scripts to reliably find the SERIAL
sequence name.
- Warn when primary/foreign key datatype mismatch requires costly lookup
+ Warn when primary/foreign key data type mismatch requires costly lookup
- New ALTER INDEX command to allow moving of indexes between tablespaces
- (Gavin)
+ New ALTER INDEX command to allow moving of indexes
+ between tablespaces (Gavin)
- Have ALTER TABLE OWNER change dependent sequence ownership too (Alvaro)
- (Gavin)
+ Have ALTER TABLE OWNER change dependent sequence
+ ownership too (Alvaro)
- Add ALSO keyword to CREATE RULE (Fabien
+ Add keyword to CREATE RULE (Fabien
Coelho)
- This allows ALSO to be added to rule creation to contrast it with
- INSTEAD rules.
+ This allows to be added to rule creation to contrast it with
+ rules.
- Add NOWAIT option to LOCK (Tatsuo)
+ Add option to LOCK (Tatsuo)
This allows the LOCK command to fail if it
In 7.3 and 7.4, a long-running btree index build could block concurrent
- CHECKPOINTs from completing, thereby causing WAL bloat because the
+ CHECKPOINTs from completing, thereby causing WAL bloat because the
WAL log could not be recycled.
- New pg_ctl >kill option for Win32 (Andrew)
+ New
pg_ctl >kill option for Win32 (Andrew)
Win32 does not have a kill command to send signals to
- backends so this capability was added to pg_ctl.
+ backends so this capability was added to
pg_ctl.
- Add --pwfile option to
initdb so the
- initial password can be set by GUI tools (Magnus)
+ Add
+
initdb so the initial password can be
+ set by GUI tools (Magnus)
- Add Win32 service "register" command to pg_ctl (Dave Page)
+ Add Win32 service
Reject non-rectangular array values as erroneous (Joe)
- Formerly, <literal>array_in> would silently build a
+ Formerly, <function>array_in> would silently build a
surprising result.
- The arithmetic operators associated with the char data typ
e
- have been removed.
+ 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 <quote>char column, you can cast it to integer.
+ to do arithmetic on a <type>"char" column, you can cast it to integer.
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.
+ Junk that was previously allowed in odd places with odd results
+ now causes an ERROR, for example, non-whitespace
+ after the closing right brace.
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 taken over to mean a NULL
+ nothing at all appears will probably be considered to be a NULL
element value in some future release.
- Accept YYYY-monthname-DD as a date string (Tom)
+ Accept YYYY-monthname-DD as a date string (Tom)
- Make netmask() and hostmask() functions return maximum-length
- masklen (Tom)
+ Make netmask() and hostmask() functions
+ return maximum-length masklen (Tom)
- to_char/to_date date conversion improvements (Kurt Roeckx, Fabien Coelho)
+ >to_char>/>/to_date() date conversion
+ improvements (Kurt Roeckx, Fabien Coelho)
- Make length() disregard trailing spaces in CHAR(n) (Gavin)
+ 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().
+ semantically insignificant in CHAR(n) data, so they
+ should not be counted by length().
- Warn of empty string being passed to oid/float4/float8 data types (Neil)
+ Warn of empty string being passed to
+ OID/float4/float8 data types (Neil)
8.1 will throw an error instead.
- Allow int2/int4/int8/float4/float8 input routines to have leading
- or trailing whitespace (Neil)
+ Allow
+ int2/int4/int8/float4/float8>/>
+ input routines to have leading or trailing whitespace
+ (Neil)
- Better support for IEEE Infinity and NaN values in
- float4, float8 (Neil)
+ Better support for IEEE Infinity and NaN
+ values in float4/float8 (Neil)
These should now work on all platforms that support IEEE-compliant
- Add "week" to date_trunc options (Robert Creager)
+ Add (Robert Creager)
- Fix to_char for 1 BC (previously it returned 1 AD) (Bruce)
+ Fix to_char for 1 BC (previously it returned
+ 1 AD) (Bruce)
- Fix to_char(year) for BC dates (previously it returned one less than
- the correct year) (Bruce)
+ Fix to_char(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)
+ Fix date_part() to return the proper millennium and
+ century (Fabien Coelho)
In previous versions, the century and millennium results had a wrong
- Add ceiling() as an alias for ceil(), and power() as an alias for pow()
- for standards compliance (Neil)
+ 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 SQL2003
- (Neil)
+ Change ln(), log(),
+ power(), and sqrt() to emit the correct
+ SQLSTATE error codes for certain error conditions, as
+ specified by SQL2003 (Neil)
- Add width_bucket() function as defined by SQL2003 (Neil)
+ Add width_bucket() function as defined by SQL2003 (Neil)
- Add generate_series() functions to simplify working with numeric sets (Joe)
+ Add generate_series() functions to simplify working
+ with numeric sets (Joe)
- Fix upper/lower/initcap functions to work with multibyte encodings (Tom)
+ Fix upper/lower/initcap() functions to work with
+ multibyte encodings (Tom)
- Add boolean and bitwise integer AND/OR aggregates (Fabien Coelho)
+ Add boolean and bitwise integer
+ aggregates (Fabien Coelho)
- Add interval plus datetime operators (Tom)
+ Add interval plus datetime operators (Tom)
- The reverse ordering, datetime plus interval, was already supported,
- but both are required by the SQL standard.
+ 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
+ Casting an integer to BIT(N) selects the rightmost N bits
+ of the integer
(Tom)
- Detect overflow of integer arithmetic (Tom)
-
-
-
-
- Remove arithmetic operators for one-byte character type/"char" (Tom)
-
- The data type can be cast to 'int' to perform such operations.
-
-
-
-
- Require CIDR values to have all non-masked bits be zero (Kevin Brintnall)
+ Require CIDR values to have all non-masked bits be zero
+ (Kevin Brintnall)
- Non-deferred AFTER triggers are now fired immediately after completion
- of the triggering query, rather than upon finishing the current
- interactive command. This makes a difference when the triggering query
- occurred within a function: the trigger is invoked before the function
- proceeds to its next operation. For example, if a function inserts
- a new row into a table, any non-deferred foreign key checks occur
- before proceeding with the function.
+ Non-deferred
+ after completion of the triggering query, rather than upon
+ finishing the current interactive command. This makes a difference
+ when the triggering query occurred within a function: the trigger
+ is invoked before the function proceeds to its next operation. For
+ example, if a function inserts a new row into a table, any
+ non-deferred foreign key checks occur before proceeding with the
+ function.
Improve parsing of PL/pgSQL FOR loops (Tom)
- Parsing is now driven by presence of ".." rather than datatype of FOR
- variable. This makes no difference for correct functions, but should
- result in more understandable error messages when a mistake is made.
+ Parsing is now driven by presence of ".." rather than
+ data type of
+ correct functions, but should result in more understandable error
+ messages when a mistake is made.
-
<span class="marked">psql</span> Changes
+
<span class="marked"><application>psql</></span> Changes
- Improve psql information display about database objects (Christopher)
+ Improve
psql information display about database+ objects (Christopher)
- Allow psql to display group membership in \du and \dg (Markus Bertheau)
+ Allow
psql to display group membership in+ \du and \dg (Markus Bertheau)
- Prevent psql \dn from showing temporary schemas (Bruce)
+ Prevent
psql \dn from showing+ temporary schemas (Bruce)
- Allow psql to handle tilde user expansion for file names (Zach Irmen)
+ 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)
+ Allow
psql to display fancy prompts, including+
color, via readline (Reece Hart, Chet Ramey)
- Make psql \copy match COPY command syntax
+ Make
psql \copy match
COPY command syntax
fully (Tom)
- Add CLUSTER information to psql \d display
+ Add
CLUSTER information to
psql+ \d display
(Bruce)
- Change psql \copy stdin/stdout to read from command input/output (Bruce)
+ Change
psql \copy stdin/stdout to read+ from command input/output (Bruce)
- Add pstdin/pstdout to read from psql's stdin/stdout (Mark Feit)
+ Add
+
psql's stdin/stdout (Mark+ Feit)
- Add global psql config file, psqlrc.sample
+ Add global
psql config file,
psqlrc.sample (Bruce)
- This allows a central file where global psql startup commands can
+ 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)
+ 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
+ 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
+ Have \dn+ show permissions and description for schemas (Dennis
Bjorklund)
-
<span class="marked">pg_dump</span> Changes
+
<span class="marked"><application>pg_dump</></span> Changes
- Use dependency information to improve the reliability of pg_dump (Tom)
+ Use dependency information to improve the reliability of
- Have pg_dump output objects in alphabetical order if possible (Tom)
+ Have
pg_dump output objects in alphabetical order if possible (Tom)
This should make it easier to identify changes between
- Allow pg_restore to ignore some SQL errors (Fabien Coelho)
+ Allow
g_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.
+ 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 -l display now includes objects' schema names
+
pg_restore + objects' schema names
- New begin/end markers in pg_dump text output (Bruce)
+ New begin/end markers in
pg_dump text output (Bruce)
- Add start/stop times for pg_dump/pg_dumpall in verbose mode (Bruce)
+ Add start/stop times for
+
pg_dump/pg_dumpall in verbose mode+ (Bruce)
- Allow most pg_dump options in pg_dumpall (Christopher)
+ Allow most
pg_dump options in+
pg_dumpall (Christopher)
- Have pg_dump use ALTER OWNER rather than SET SESSION
- AUTHORIZATION by default (Christopher)
+ Have
pg_dump use ALTER OWNER rather+ than SET SESSION AUTHORIZATION by default
+ (Christopher)
- Make libpq SIGPIPE thread-safe (Bruce)
+ Make libpq thread-safe (Bruce)
- Add PQmbdsplen() which returns the "display length" of a character (Tatsuo)
+ Add PQmbdsplen() which returns the display length
+ of a character (Tatsuo)
- Add thread locking to SSL and Kerberos connections (Manfred Spraul)
+ Add thread locking to
SSL and+
Kerberos connections (Manfred Spraul)
- Allow PQoidValue(), PQcmdTuples(), and PQoidStatus() to work on
- EXECUTE commands (Neil)
+ 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 PQserverVersion() to provide more convenient
+ access to the server version number (Greg Sabino Mullane)
- Many ecpg fixes, including SET DESCRIPTOR (Michael)
+ Many ecpg improvements, including SET DESCRIPTOR (Michael)
- Add PQprepare()/PQsendPrepared() functions to support preparing
- statements without necessarily specifying the datatypes of their parameters
- (Abhijit Menon-Sen)
+ Add PQprepare/PQsendPrepared() functions to support
+ preparing statements without necessarily specifying the data types
+ of their parameters (Abhijit Menon-Sen)
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.
+ 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 --with-docdir to choose installation location of documentation; also
- allow --infodir (Peter)
+ Use to choose installation location of documentation; also
+ allow (Peter)
- Add --without-docdir to prevent installation of documentation (Peter)
+ Add to prevent installation of documentation (Peter)
- Upgrade to DocBook V4.2 SGML (Peter)
+ Upgrade to
DocBook V4.2 SGML (Peter)
- New "PostgreSQL" CVS tag (Marc)
+ 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
+ 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.
- Add inlined test-and-set code on PA-RISC for gcc (ViSolve, Tom)
+ Add inlined test-and-set code on PA-RISC for
gcc+ (ViSolve, Tom)
- Clean up spinlock assembly code to avoid warnings from newer gcc
- releases (Tom)
+ Clean up spinlock assembly code to avoid warnings from newer
-
More accurately estimate memory and file descriptor usage (Tom)
- New fsync test program (Bruce)
+ New fsync() test program (Bruce)
-
- Remove contrib/rserv: obsoleted by various separate projects
-
-
-
Remove
pg_encoding; not needed
- Auto detect thread flags (no more manual testing) (Bruce)
+ Auto-detect thread flags (no more manual testing) (Bruce)
- Use Olson's public domain timezone library (Magnus)
+ Use Olson's public domain
timezone library (Magnus)
- psql now uses a flex-generated lexical analyzer to process command strings
+
psql now uses a flex-generated+ lexical analyzer to process command strings
- New pgevent for Win32 logging
+ New
pgevent for Win32 logging
- Remove /contrib/rserv
+ Allow /contrib/pg_autovacuum to run as a Win32 service (Dave Page)
- Allow /contrib/pg_autovacuum to run as a Win32 service (Dave Page)
+ Add functions to /contrib/dbsize (Andreas Pflug)
- Add functions to /contrib/dbsize (Andreas Pflug)
+ Remove contrib/pg_logger
- Remove contrib/pg_logger
+ Remove contrib/rserv: obsoleted by various separate projects
Very large left joins using a hash join plan could fail to output unmatched
left-side rows given just the right data distribution.
-
Disallow running pg_ctl as root+
Disallow running pg_ctl as root This is to guard against any possible security issues.
Force cache update after renaming a column in a foreign key
Pretty-print UNION queries correctly
Make psql handle \r\n newlines properly in COPY IN
-
pg_dump handled ACLs with grant options incorrectly+
pg_dump handled ACLs with grant options incorrectly Fix thread support for OS X and Solaris
Updated JDBC driver (build 215) with various fixes
projects / postgresql.git / commitdiff