PostgreSQL is Copyright © 1996-9 by the Postgres Global Development Group.
Table of Contents
- Release 6.5.2
- Migration to v6.5.2
- Detailed Change List
- Release 6.5.1
- Migration to v6.5.1
- Detailed Change List
- Release 6.5
- Migration to v6.5
- Multi-Version Concurrency Control
- Detailed Change List
- Release 6.4.2
- Migration to v6.4.2
- Detailed Change List
- Release 6.4.1
- Migration to v6.4.1
- Detailed Change List
- Release 6.4
- Migration to v6.4
- Detailed Change List
- Release 6.3.2
- Detailed Change List
- Release 6.3.1
- Detailed Change List
- Release 6.3
- Migration to v6.3
- Detailed Change List
- Release 6.2.1
- Migration from v6.2 to v6.2.1
- Detailed Change List
- Release 6.2
- Migration from v6.1 to v6.2
- Migration from v1.x to v6.2
- Detailed Change List
- Release 6.1.1
- Migration from v6.1 to v6.1.1
- Detailed Change List
- Release 6.1
- Migration to v6.1
- Detailed Change List
- Release v6.0
- Migration from v1.09 to v6.0
- Migration from pre-v1.09 to v6.0
- Detailed Change List
- Release v1.09
- Release v1.02
- Migration from v1.02 to v1.02.1
- Dump/Reload Procedure
- Detailed Change List
- Release v1.01
- Migration from v1.0 to v1.01
- Detailed Change List
- Release v1.0
- Detailed Change List
- Postgres95 Beta 0.03
- Detailed Change List
- Postgres95 Beta 0.02
- Detailed Change List
- Postgres95 Beta 0.01
+ Release 6.5.3
+ Migration to v6.5.3
+ Detailed Change List
+ Release 6.5.2
+ Migration to v6.5.2
+ Detailed Change List
+ Release 6.5.1
+ Migration to v6.5.1
+ Detailed Change List
+ Release 6.5
+ Migration to v6.5
+ Multi-Version Concurrency Control
+ Detailed Change List
+ Release 6.4.2
+ Migration to v6.4.2
+ Detailed Change List
+ Release 6.4.1
+ Migration to v6.4.1
+ Detailed Change List
+ Release 6.4
+ Migration to v6.4
+ Detailed Change List
+ Release 6.3.2
+ Detailed Change List
+ Release 6.3.1
+ Detailed Change List
+ Release 6.3
+ Migration to v6.3
+ Detailed Change List
+ Release 6.2.1
+ Migration from v6.2 to v6.2.1
+ Detailed Change List
+ Release 6.2
+ Migration from v6.1 to v6.2
+ Migration from v1.x to v6.2
+ Detailed Change List
+ Release 6.1.1
+ Migration from v6.1 to v6.1.1
+ Detailed Change List
+ Release 6.1
+ Migration to v6.1
+ Detailed Change List
+ Release v6.0
+ Migration from v1.09 to v6.0
+ Migration from pre-v1.09 to v6.0
+ Detailed Change List
+ Release v1.09
+ Release v1.02
+ Migration from v1.02 to v1.02.1
+ Dump/Reload Procedure
+ Detailed Change List
+ Release v1.01
+ Migration from v1.0 to v1.01
+ Detailed Change List
+ Release v1.0
+ Detailed Change List
+ Postgres95 Beta 0.03
+ Detailed Change List
+ Postgres95 Beta 0.02
+ Detailed Change List
+ Postgres95 Beta 0.01
+
+
+Release 6.5.3
+
+ This is basically a cleanup release for 6.5.2. We have added a
+ new pgaccess that was missing in 6.5.2, and installed an
+ NT-specific fix.
+
+Migration to v6.5.3
+
+ A dump/restore is not required for those running 6.5.*.
+
+Detailed Change List
+
+ Updated version of pgaccess 0.98
+ NT-specific patch
+
Release 6.5.2
- This is basically a cleanup release for 6.5.1. We have fixed a
+ This is basically a cleanup release for 6.5.1. We have fixed a
variety of problems reported by 6.5.1 users.
Migration to v6.5.2
Release 6.5.1
- This is basically a cleanup release for 6.5. We have fixed a
+ This is basically a cleanup release for 6.5. We have fixed a
variety of problems reported by 6.5 users.
Migration to v6.5.1
Release 6.5
- This release marks a major step in the development team's mastery
+ This release marks a major step in the development team's mastery
of the source code we inherited from Berkeley. You will see we are
now easily adding major features, thanks to the increasing size and
experience of our world-wide development team.
- Here is a brief summary of the more notable changes:
-
- Multi-version concurrency control(MVCC)
- This removes our old table-level locking, and replaces it with a
- locking system that is superior to most commercial database
- systems. In a traditional system, each row that is modified is
- locked until committed, preventing reads by other users. MVCC
- uses the natural multi-version nature of PostgreSQL to allow
- readers to continue reading consistent data during writer
- activity. Writers continue to use the compact pg_log transaction
- system. This is all performed without having to allocate a lock
- for every row like traditional database systems. So, basically,
- we no longer are restricted by simple table-level locking; we
- have something better than row-level locking.
-
- Hot backups from pg_dump
- pg_dump takes advantage of the new MVCC features to give a
- consistant database dump/backup while the database stays online
- and available for queries.
-
- Numeric data type
- We now have a true numeric data type, with user-specified
- precision.
-
- Temporary tables
- Temporary tables are guaranteed to have unique names within a
- database session, and are destroyed on session exit.
-
- New SQL features
- We now have CASE, INTERSECT, and EXCEPT statement support. We
- have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, SELECT
- ... FOR UPDATE, and an improved LOCK TABLE command.
-
- Speedups
- We continue to speed up PostgreSQL, thanks to the variety of
- talents within our team. We have sped up memory allocation,
- optimization, table joins, and row transfer routines.
-
- Ports
- We continue to expand our port list, this time including
- WinNT/ix86 and NetBSD/arm32.
-
- Interfaces
- Most interfaces have new versions, and existing functionality
- has been improved.
-
- Documentation
- New and updated material is present throughout the
- documentation. New FAQs have been contributed for SGI and AIX
- platforms. The Tutorial has introductory information on SQL from
- Stefan Simkovics. For the User's Guide, there are reference pages
- covering the postmaster and more utility programs, and a new
- appendix contains details on date/time behavior. The
- Administrator's Guide has a new chapter on troubleshooting from
- Tom Lane. And the Programmer's Guide has a description of query
- processing, also from Stefan, and details on obtaining the
- Postgres source tree via anonymous CVS and CVSup.
-
+ Here is a brief summary of the more notable changes:
+
+ Multi-version concurrency control(MVCC)
+ This removes our old table-level locking, and replaces it with a
+ locking system that is superior to most commercial database
+ systems. In a traditional system, each row that is modified is
+ locked until committed, preventing reads by other users. MVCC
+ uses the natural multi-version nature of PostgreSQL to allow
+ readers to continue reading consistent data during writer
+ activity. Writers continue to use the compact pg_log transaction
+ system. This is all performed without having to allocate a lock
+ for every row like traditional database systems. So, basically,
+ we no longer are restricted by simple table-level locking; we
+ have something better than row-level locking.
+
+ Hot backups from pg_dump
+ pg_dump takes advantage of the new MVCC features to give a
+ consistant database dump/backup while the database stays online
+ and available for queries.
+
+ Numeric data type
+ We now have a true numeric data type, with user-specified
+ precision.
+
+ Temporary tables
+ Temporary tables are guaranteed to have unique names within a
+ database session, and are destroyed on session exit.
+
+ New SQL features
+ We now have CASE, INTERSECT, and EXCEPT statement support. We
+ have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, SELECT
+ ... FOR UPDATE, and an improved LOCK TABLE command.
+
+ Speedups
+ We continue to speed up PostgreSQL, thanks to the variety of
+ talents within our team. We have sped up memory allocation,
+ optimization, table joins, and row transfer routines.
+
+ Ports
+ We continue to expand our port list, this time including
+ WinNT/ix86 and NetBSD/arm32.
+
+ Interfaces
+ Most interfaces have new versions, and existing functionality
+ has been improved.
+
+ Documentation
+ New and updated material is present throughout the
+ documentation. New FAQs have been contributed for SGI and AIX
+ platforms. The Tutorial has introductory information on SQL from
+ Stefan Simkovics. For the User's Guide, there are reference pages
+ covering the postmaster and more utility programs, and a new
+ appendix contains details on date/time behavior. The
+ Administrator's Guide has a new chapter on troubleshooting from
+ Tom Lane. And the Programmer's Guide has a description of query
+ processing, also from Stefan, and details on obtaining the
+ Postgres source tree via anonymous CVS and CVSup.
+
Migration to v6.5
- A dump/restore using pg_dump is required for those wishing to
+ A dump/restore using pg_dump is required for those wishing to
migrate data from any previous release of Postgres. pg_upgrade can
not be used to upgrade to this release because the on-disk structure
of the tables has changed compared to previous releases.
- The new Multi-Version Concurrency Control (MVCC) features can give
+ The new Multi-Version Concurrency Control (MVCC) features can give
somewhat different behaviors in multi-user environments. Read and
understand the following section to ensure that your existing
applications will give you the behavior you need.
Multi-Version Concurrency Control
- Because readers in 6.5 don't lock data, regardless of transaction
+ Because readers in 6.5 don't lock data, regardless of transaction
isolation level, data read by one transaction can be overwritten by
another. In other words, if a row is returned by SELECT it doesn't
mean that this row really exists at the time it is returned (i.e.
is protected from being deleted or updated by concurrent
transactions before the current transaction does a commit or
rollback.
- To ensure the actual existence of a row and protect it against
+ To ensure the actual existence of a row and protect it against
concurrent updates one must use SELECT FOR UPDATE or an appropriate
LOCK TABLE statement. This should be taken into account when porting
applications from previous releases of Postgres and other
environments.
- Keep the above in mind if you are using contrib/refint.* triggers
+ Keep the above in mind if you are using contrib/refint.* triggers
for referential integrity. Additional technics are required now. One
way is to use LOCK parent_table IN SHARE ROW EXCLUSIVE MODE command
if a transaction is going to update/delete a primary key and use
LOCK parent_table IN SHARE MODE command if a transaction is going to
update/insert a foreign key.
- Note: Note that if you run a transaction in SERIALIZABLE mode
- then you must execute the LOCK commands above before execution of
- any DML statement (SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO) in
- the transaction.
+ Note: Note that if you run a transaction in SERIALIZABLE mode
+ then you must execute the LOCK commands above before execution of
+ any DML statement (SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO) in
+ the transaction.
-
- These inconveniences will disappear in the future when the ability
+
+ These inconveniences will disappear in the future when the ability
to read dirty (uncommitted) data (regardless of isolation level) and
true referential integrity will be implemented.
Enable right-hand queries by default(Bruce)
Allow reliable maximum number of backends to be set at configure
time
- (--with-maxbackends and postmaster switch (-N backends))(Tom)
+ (--with-maxbackends and postmaster switch (-N backends))(Tom)
GEQO default now 10 tables because of optimizer speedups(Tom)
Allow NULL=Var for MS-SQL portability(Michael, Bruce)
Modify contrib check_primary_key() so either "automatic" or
Improve file handling to be more uniform, prevent file descriptor
leak(Tom)
New install commands for plpgsql(Jan)
-
+
Release 6.4.2
The 6.4.1 release was improperly packaged. This also has one
Add pg_dump -N flag to force double quotes around identifiers. This
is
- the default(Thomas)
+ the default(Thomas)
Fix for NOT in where clause causing crash(Bruce)
EXPLAIN VERBOSE coredump fix(Vadim)
Fix shared-library problems on Linux
Fix test for table existance to allow mixed-case and whitespace in
- the table name(Thomas)
+ the table name(Thomas)
Fix a couple of pg_dump bugs
Configure matches template/.similar entries better(Tom)
Change builtin function names from SPI_* to spi_*
has received some attention since the previous release. Here is a
brief, incomplete summary:
o Views and rules are now functional thanks to extensive new code in
- the rewrite rules system from Jan Wieck. He also wrote a chapter
- on it for the Programmer's Guide.
+ the rewrite rules system from Jan Wieck. He also wrote a chapter
+ on it for the Programmer's Guide.
o Jan also contributed a second procedural language, PL/pgSQL, to go
- with the original PL/pgTCL procedural language he contributed last
- release.
+ with the original PL/pgTCL procedural language he contributed last
+ release.
o We have optional multiple-byte character set support from Tatsuo
- Iishi to complement our existing locale support.
+ Iishi to complement our existing locale support.
o Client/server communications has been cleaned up, with better
- support for asynchronous messages and interrupts thanks to Tom
- Lane.
+ support for asynchronous messages and interrupts thanks to Tom
+ Lane.
o The parser will now perform automatic type coersion to match
- arguments to available operators and functions, and to match
- columns and expressions with target columns. This uses a generic
- mechanism which supports the type extensibility features of
- Postgres. There is a new chapter in the User's Guide which covers
- this topic.
+ arguments to available operators and functions, and to match
+ columns and expressions with target columns. This uses a generic
+ mechanism which supports the type extensibility features of
+ Postgres. There is a new chapter in the User's Guide which covers
+ this topic.
o Three new data types have been added. Two types, inet and cidr,
- support various forms of IP network, subnet, and machine
- addressing. There is now an 8-byte integer type available on some
- platforms. See the chapter on data types in the User's Guide for
- details. A fourth type, serial, is now supported by the parser as
- an amalgam of the int4 type, a sequence, and a unique index.
+ support various forms of IP network, subnet, and machine
+ addressing. There is now an 8-byte integer type available on some
+ platforms. See the chapter on data types in the User's Guide for
+ details. A fourth type, serial, is now supported by the parser as
+ an amalgam of the int4 type, a sequence, and a unique index.
o Several more SQL92-compatible syntax features have been added,
- including INSERT DEFAULT VALUES
+ including INSERT DEFAULT VALUES
o The automatic configuration and installation system has received
- some attention, and should be more robust for more platforms than
- it has ever been.
+ some attention, and should be more robust for more platforms than
+ it has ever been.
Migration to v6.4
------------
Upgrade ecpg and ecpglib,see src/interfaces/ecpc/ChangeLog(Michael)
Show the index used in an EXPLAIN(Zeugswetter)
- EXPLAIN invokes rule system and shows plan(s) for rewritten
+ EXPLAIN invokes rule system and shows plan(s) for rewritten
queries(Jan)
Multi-byte awareness of many data types and functions, via
configure(Tatsuo)
Allow NOT LIKE, IN, NOT IN, BETWEEN, and NOT BETWEEN
constraint(Thomas)
New rewrite system fixes many problems with rules and views(Jan)
- * Rules on relations work
- * Event qualifications on insert/update/delete work
- * New OLD variable to reference CURRENT, CURRENT will be
+ * Rules on relations work
+ * Event qualifications on insert/update/delete work
+ * New OLD variable to reference CURRENT, CURRENT will be
remove in future
- * Update rules can reference NEW and OLD in rule
+ * Update rules can reference NEW and OLD in rule
qualifications/actions
- * Insert/update/delete rules on views work
- * Multiple rule actions are now supported, surrounded by
+ * Insert/update/delete rules on views work
+ * Multiple rule actions are now supported, surrounded by
parentheses
- * Regular users can create views/rules on tables they have
+ * Regular users can create views/rules on tables they have
RULE permits
- * Rules and views inherit the permissions on the creator
- * No rules at the column level
- * No UPDATE NEW/OLD rules
- * New pg_tables, pg_indexes, pg_rules and pg_views system
+ * Rules and views inherit the permissions on the creator
+ * No rules at the column level
+ * No UPDATE NEW/OLD rules
+ * New pg_tables, pg_indexes, pg_rules and pg_views system
views
- * Only a single action on SELECT rules
- * Total rewrite overhaul, perhaps for 6.5
- * handle subselects
- * handle aggregates on views
- * handle insert into select from view works
+ * Only a single action on SELECT rules
+ * Total rewrite overhaul, perhaps for 6.5
+ * handle subselects
+ * handle aggregates on views
+ * handle insert into select from view works
System indexes are now multi-key(Bruce)
Oidint2, oidint4, and oidname types are removed(Bruce)
Use system cache for more system table lookups(Bruce)
v6.3 for a more complete summary of new features.
Summary:
o Repairs automatic configuration support for some platforms,
- including Linux, from breakage inadvertently introduced in v6.3.1.
+ including Linux, from breakage inadvertently introduced in v6.3.1.
o Correctly handles function calls on the left side of BETWEEN and
- LIKE clauses.
+ LIKE clauses.
A dump/restore is NOT required for those running 6.3 or 6.3.1. A
'make distclean', 'make', and 'make install' is all that is
required. This last step should be performed while the postmaster is
There are many new features and improvements in this release. Here
is a brief, incomplete summary:
o Many new SQL features, including full SQL92 subselect capability
- (everything is here but target-list subselects).
+ (everything is here but target-list subselects).
o Support for client-side environment variables to specify time zone
- and date style.
+ and date style.
o Socket interface for client/server connection. This is the default
- now so you may need to start postmaster with the ?-i? flag.
+ now so you may need to start postmaster with the ?-i? flag.
o Better password authorization mechanisms. Default table
- permissions have changed.
+ permissions have changed.
o Old-style ?time travel? has been removed. Performance has been
- improved.
+ improved.
- Note: Bruce Momjian wrote the following notes to introduce the
- new release.
+ Note: Bruce Momjian wrote the following notes to introduce the
+ new release.
There are some general 6.3 issues that I want to mention. These are
only the big items that can not be described in one sentence. A
Fix substr() for out-of-bounds data
Fix for select 1=1 or 2=2, select 1=1 and 2=2, and select
sum(2+2)(Bruce)
- Fix notty output to show status result. -q option still turns it
+ Fix notty output to show status result. -q option still turns it
off(Bruce)
Fix for count(*), aggs with views and multiple tables and
sum(3)(Bruce)
Fix cluster(Bruce)
Fix for PQtrace start/stop several times(Bruce)
Fix a variety of locking problems like newer lock waiters getting
- lock before older waiters, and having readlock people not
+ lock before older waiters, and having readlock people not
share
- locks if a writer is waiting for a lock, and waiting writers
+ locks if a writer is waiting for a lock, and waiting writers
not
- getting priority over waiting readers(Bruce)
+ getting priority over waiting readers(Bruce)
Fix crashes in psql when executing queries from external
files(James)
Fix problem with multiple order by columns, with the first one
having
- NULL values(Jeroen)
+ NULL values(Jeroen)
Use correct hash table support functions for float8 and int4(Thomas)
Re-enable JOIN= option in CREATE OPERATOR statement (Thomas)
Change precedence for boolean operators to match expected
Generate elog(ERROR) on over-large integer(Bruce)
Allow multiple-argument functions in constraint clauses(Thomas)
Check boolean input literals for 'true','false','yes','no','1','0'
- and throw elog(ERROR) if unrecognized(Thomas)
+ and throw elog(ERROR) if unrecognized(Thomas)
Major large objects fix
Fix for GROUP BY showing duplicates(Vadim)
Fix for index scans in MergeJion(Vadim)
Speedup by inlining some frequently-called functions
Real deadlock detection, no more timeouts(Bruce)
Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
- CURRENT_USER(Thomas)
+ CURRENT_USER(Thomas)
Modify constraint syntax to be SQL92-compliant(Thomas)
Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas)
Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
Implement SQL92 binary and hexadecimal string decoding (b'10' and
x'1F')(Thomas)
Support SQL92 syntax for type coercion of literal strings
- (e.g. "DATETIME 'now'")(Thomas)
+ (e.g. "DATETIME 'now'")(Thomas)
Add conversions for int2, int4, and OID types to and from
text(Thomas)
Use shared lock when building indices(Vadim)
Free memory allocated for an user query inside transaction block
after
- this query is done, was turned off in <= 6.2.1(Vadim)
+ this query is done, was turned off in <= 6.2.1(Vadim)
New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)
New Postgres Procedural Language (PL) backend interface(Jan)
Rename pg_dump -H option to -h(Bruce)
Add PGDATESTYLE environment variable to frontend and backend
initialization(Thomas)
Add PGTZ, PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO
- frontend library initialization environment
+ frontend library initialization environment
variables(Thomas)
Regression tests time zone automatically set with "setenv PGTZ
PST8PDT"(Thomas)
Add pg_description table for info on tables, columns, operators,
types, and
- aggregates(Bruce)
+ aggregates(Bruce)
Increase 16 char limit on system table/index names to 32
characters(Bruce)
Rename system indices(Bruce)
Remove archive stuff(Bruce)
Allow for a pg_password authentication database that is separate
from
- the system password file(Todd)
+ the system password file(Todd)
Dump ACLs, GRANT, REVOKE permissions(Matt)
Define text, varchar, and bpchar string length functions(Thomas)
Fix Query handling for inheritance, and cost computations(Bruce)
Add report of offending line when COPY command fails
Allow VIEW permissions to be set separately from the underlying
tables.
- For security, use GRANT/REVOKE on views as appropriate(Jan)
+ For security, use GRANT/REVOKE on views as appropriate(Jan)
Tables now have no default GRANT SELECT TO PUBLIC. You must
- explicitly grant such permissions.
+ explicitly grant such permissions.
Clean up tutorial examples(Darren)
Source Tree Changes
Add script to check regression test results
Break parser functions into smaller files, group together(Bruce)
Rename heap_create to heap_create_and_catalog, rename heap_creatr
- to heap_create()(Bruce)
+ to heap_create()(Bruce)
Sparc/Linux patch for locking(TomS)
Remove PORTNAME and reorganize port-specific stuff(Marc)
Add optimizer README file(Bruce)
Fix for libptcl make(Tatsuo)
AIX patch(Darren)
Change IS TRUE, IS FALSE, ... to expressions using "=" rather than
- function calls to istrue() or isfalse() to allow
+ function calls to istrue() or isfalse() to allow
optimization(Thomas)
Various fixes NetBSD/Sparc related(TomH)
Alpha linux locking(Travis,Ryan)
Summary:
o Allow strings to span lines, per SQL92.
o Include example trigger function for inserting user names on table
- updates.
+ updates.
This is a minor bug-fix release on v6.2. For upgrades from pre-v6.2
systems, a full dump/reload is required. Refer to the v6.2 release
notes for instructions.
Another way to avoid dump/reload is to use the following SQL command
from psql to update the existing system table:
- update pg_aggregate set aggfinalfn = 'cash_div_flt8'
- where aggname = 'avg' and aggbasetype = 790;
+ update pg_aggregate set aggfinalfn = 'cash_div_flt8'
+ where aggname = 'avg' and aggbasetype = 790;
This will need to be done to every existing database, including
template1.
tables(Bruce)
Fix compile errors on overflow due to shifts, unsigned, and bad
prototypes
- from Solaris(Diab Jerius)
+ from Solaris(Diab Jerius)
Fix bugs in geometric line arithmetic (bad intersection
calculations)(Thomas)
Check for geometric intersections at endpoints to avoid rounding
Change time function names to be more consistent(Michael Reifenberg)
Check for zero divides(Michael Reifenberg)
Fix very old bug which made tuples changed/inserted by a commnd
- visible to the command itself (so we had multiple update of
- updated tuples, etc)(Vadim)
+ visible to the command itself (so we had multiple update of
+ updated tuples, etc)(Vadim)
Fix for SELECT null, 'fail' FROM pg_am (Patrick)
SELECT NULL as EMPTY_FIELD now allowed(Patrick)
Remove un-needed signal stuff from contrib/pginterface
(Vadim)
Fix time_cmp function (Vadim)
Fix handling of functions with non-attribute first argument in
- WHERE clauses (Vadim)
+ WHERE clauses (Vadim)
Fix GROUP BY when order of entries is different from order
- in target list (Vadim)
+ in target list (Vadim)
Fix pg_dump for aggregates without sfunc1 (Vadim)
Enhancements
Triggers implemented with CREATE TRIGGER (SQL3)(Vadim)
SPI (Server Programming Interface) allows execution of queries
inside
- C-functions (Vadim)
+ C-functions (Vadim)
NOT NULL implemented (SQL92)(Robson Paniago de Miranda)
Include reserved words for string handling, outer joins, and
unions(Thomas)
Support WITH TIME ZONE syntax (SQL92)(Thomas)
Support INTERVAL unit TO unit syntax (SQL92)(Thomas)
Define types DOUBLE PRECISION, INTERVAL, CHARACTER,
- and CHARACTER VARYING (SQL92)(Thomas)
+ and CHARACTER VARYING (SQL92)(Thomas)
Define type FLOAT(p) and rudimentary DECIMAL(p,s), NUMERIC(p,s)
(SQL92)(Thomas)
Define EXTRACT(), POSITION(), SUBSTRING(), and TRIM()
Add center() routines for lseg, path, polygon(Thomas)
Add distance() routines for circle-polygon, polygon-polygon(Thomas)
Check explicitly for points and polygons contained within polygons
- using an axis-crossing algorithm(Thomas)
+ using an axis-crossing algorithm(Thomas)
Add routine to convert circle-box(Thomas)
Merge conflicting operators for different geometric data
types(Thomas)
Release 6.1
- The regression tests have been adapted and extensively modified for
+ The regression tests have been adapted and extensively modified for
the v6.1 release of Postgres.
- Three new data types (datetime, timespan, and circle) have been
+ Three new data types (datetime, timespan, and circle) have been
added to the native set of Postgres types. Points, boxes, paths, and
polygons have had their output formats made consistant across the
data types. The polygon output in misc.out has only been
spot-checked for correctness relative to the original regression
output.
- Postgres v6.1 introduces a new, alternate optimizer which uses
+ Postgres v6.1 introduces a new, alternate optimizer which uses
genetic algorithms. These algorithms introduce a random behavior in
the ordering of query results when the query contains multiple
qualifiers or multiple tables (giving the optimizer a choice on
inherently unordered (e.g. points and time intervals) and tests
involving those types are explicitly bracketed with set geqo to
'off' and reset geqo.
- The interpretation of array specifiers (the curly braces around
+ The interpretation of array specifiers (the curly braces around
atomic values) appears to have changed sometime after the original
regression tests were generated. The current ./expected/*.out files
reflect this new interpretation, which may not be correct!
- The float8 regression test fails on at least some platforms. This
+ The float8 regression test fails on at least some platforms. This
is due to differences in implementations of pow() and exp() and the
signaling mechanisms used for overflow and underflow conditions.
- The "random" results in the random test should cause the "random"
+ The "random" results in the random test should cause the "random"
test to be "failed", since the regression tests are evaluated using
a simple diff. However, "random" does not seem to produce random
results on my test machine (Linux/gcc/i686).
Here is a new migration file for 1.02.1. It includes the 'copy'
change and a script to convert old ascii files.
- Note: The following notes are for the benefit of users who want
- to migrate databases from postgres95 1.01 and 1.02 to postgres95
- 1.02.1.
- If you are starting afresh with postgres95 1.02.1 and do not need
- to migrate old databases, you do not need to read any further.
+ Note: The following notes are for the benefit of users who want
+ to migrate databases from postgres95 1.01 and 1.02 to postgres95
+ 1.02.1.
+ If you are starting afresh with postgres95 1.02.1 and do not need
+ to migrate old databases, you do not need to read any further.
In order to upgrade older postgres95 version 1.01 or 1.02 databases
to version 1.02.1, the following steps are required:
1. Start up a new 1.02.1 postmaster
2. Add the new built-in functions and operators of 1.02.1 to 1.01 or
- 1.02 databases. This is done by running the new 1.02.1 server
- against your own 1.01 or 1.02 database and applying the queries
- attached at the end of thie file. This can be done easily through
- psql. If your 1.01 or 1.02 database is named "testdb" and you
- have cut the commands from the end of this file and saved them in
- addfunc.sql:
- % psql testdb -f addfunc.sql
- Those upgrading 1.02 databases will get a warning when executing
- the last two statements in the file because they are already
- present in 1.02. This is not a cause for concern.
+ 1.02 databases. This is done by running the new 1.02.1 server
+ against your own 1.01 or 1.02 database and applying the queries
+ attached at the end of thie file. This can be done easily through
+ psql. If your 1.01 or 1.02 database is named "testdb" and you
+ have cut the commands from the end of this file and saved them in
+ addfunc.sql:
+ % psql testdb -f addfunc.sql
+ Those upgrading 1.02 databases will get a warning when executing
+ the last two statements in the file because they are already
+ present in 1.02. This is not a cause for concern.
Dump/Reload Procedure
the end-of-data marker. Also, empty strings are now loaded in as ''
rather than NULL. See the copy manual page for full details.
- sed 's/^\.$/\\./g' <in_file >out_file
+ sed 's/^\.$/\\./g' <in_file >out_file
If you are loading an older binary copy or non-stdout copy, there is
no end-of-data character, and hence no conversion necessary.
Detailed Change List
Source code maintenance and development
- * worldwide team of volunteers
- * the source tree now in CVS at ftp.ki.net
+ * worldwide team of volunteers
+ * the source tree now in CVS at ftp.ki.net
Enhancements
- * psql (and underlying libpq library) now has many more options for
- formatting output, including HTML
- * pg_dump now output the schema and/or the data, with many fixes to
- enhance completeness.
- * psql used in place of monitor in administration shell scripts.
- monitor to be depreciated in next release.
- * date/time functions enhanced
- * NULL insert/update/comparison fixed/enhanced
- * TCL/TK lib and shell fixed to work with both tck7.4/tk4.0 and
+ * psql (and underlying libpq library) now has many more options for
+ formatting output, including HTML
+ * pg_dump now output the schema and/or the data, with many fixes to
+ enhance completeness.
+ * psql used in place of monitor in administration shell scripts.
+ monitor to be depreciated in next release.
+ * date/time functions enhanced
+ * NULL insert/update/comparison fixed/enhanced
+ * TCL/TK lib and shell fixed to work with both tck7.4/tk4.0 and
tcl7.5/tk4.1
Bug Fixes (almost too numerous to mention)
- * indexes
- * storage management
- * check for NULL pointer before dereferencing
- * Makefile fixes
+ * indexes
+ * storage management
+ * check for NULL pointer before dereferencing
+ * Makefile fixes
New Ports
- * added SolarisX86 port
- * added BSDI 2.1 port
- * added DGUX port
+ * added SolarisX86 port
+ * added BSDI 2.1 port
+ * added DGUX port
Release v1.01
postgres95 version 1.0, the following steps are required:
1. Set the definition of NAMEDATALEN in src/Makefile.global to 16
- and OIDNAMELEN to 20.
+ and OIDNAMELEN to 20.
2. Decide whether you want to use Host based authentication.
- a. If you do, you must create a file name "pg_hba" in your
- top-level data directory (typically the value of your
- $PGDATA). src/libpq/pg_hba shows an example syntax.
- b. If you do not want host-based authentication, you can
- comment out the line
- HBA = 1
- in src/Makefile.global
- Note that host-based authentication is turned on by
- default, and if you do not take steps A or B above, the
- out-of-the-box 1.01 will not allow you to connect to 1.0
- databases.
+ a. If you do, you must create a file name "pg_hba" in your
+ top-level data directory (typically the value of your
+ $PGDATA). src/libpq/pg_hba shows an example syntax.
+ b. If you do not want host-based authentication, you can
+ comment out the line
+ HBA = 1
+ in src/Makefile.global
+ Note that host-based authentication is turned on by
+ default, and if you do not take steps A or B above, the
+ out-of-the-box 1.01 will not allow you to connect to 1.0
+ databases.
3. Compile and install 1.01, but DO NOT do the initdb step.
4. Before doing anything else, terminate your 1.0 postmaster, and
- backup your existing $PGDATA directory.
+ backup your existing $PGDATA directory.
5. Set your PGDATA environment variable to your 1.0 databases, but
- set up path up so that 1.01 binaries are being used.
+ set up path up so that 1.01 binaries are being used.
6. Modify the file $PGDATA/PG_VERSION from 5.0 to 5.1
7. Start up a new 1.01 postmaster
8. Add the new built-in functions and operators of 1.01 to 1.0
- databases. This is done by running the new 1.01 server against
- your own 1.0 database and applying the queries attached and
- saving in the file 1.0_to_1.01.sql. This can be done easily
- through psql. If your 1.0 database is name "testdb":
- % psql testdb -f 1.0_to_1.01.sql
- and then execute the following commands (cut and paste from
- here):
- -- add builtin functions that are new to 1.01
-
- create function int4eqoid (int4, oid) returns bool as 'foo'
- language 'internal';
- create function oideqint4 (oid, int4) returns bool as 'foo'
- language 'internal';
- create function char2icregexeq (char2, text) returns bool as
- 'foo'
- language 'internal';
- create function char2icregexne (char2, text) returns bool as
- 'foo'
- language 'internal';
- create function char4icregexeq (char4, text) returns bool as
- 'foo'
- language 'internal';
- create function char4icregexne (char4, text) returns bool as
- 'foo'
- language 'internal';
- create function char8icregexeq (char8, text) returns bool as
- 'foo'
- language 'internal';
- create function char8icregexne (char8, text) returns bool as
- 'foo'
- language 'internal';
- create function char16icregexeq (char16, text) returns bool as
- 'foo'
- language 'internal';
- create function char16icregexne (char16, text) returns bool as
- 'foo'
- language 'internal';
- create function texticregexeq (text, text) returns bool as 'foo'
- language 'internal';
- create function texticregexne (text, text) returns bool as 'foo'
- language 'internal';
-
- -- add builtin functions that are new to 1.01
-
- create operator = (leftarg = int4, rightarg = oid, procedure =
- int4eqoid);
- create operator = (leftarg = oid, rightarg = int4, procedure =
- oideqint4);
- create operator ~* (leftarg = char2, rightarg = text, procedure =
- char2icregexeq);
- create operator !~* (leftarg = char2, rightarg = text, procedure
- = char2icregexne);
- create operator ~* (leftarg = char4, rightarg = text, procedure =
- char4icregexeq);
- create operator !~* (leftarg = char4, rightarg = text, procedure
- = char4icregexne);
- create operator ~* (leftarg = char8, rightarg = text, procedure =
- char8icregexeq);
- create operator !~* (leftarg = char8, rightarg = text, procedure
- = char8icregexne);
- create operator ~* (leftarg = char16, rightarg = text, procedure
- = char16icregexeq);
- create operator !~* (leftarg = char16, rightarg = text, procedure
- = char16icregexne);
- create operator ~* (leftarg = text, rightarg = text, procedure =
- texticregexeq);
- create operator !~* (leftarg = text, rightarg = text, procedure =
- texticregexne);
+ databases. This is done by running the new 1.01 server against
+ your own 1.0 database and applying the queries attached and
+ saving in the file 1.0_to_1.01.sql. This can be done easily
+ through psql. If your 1.0 database is name "testdb":
+ % psql testdb -f 1.0_to_1.01.sql
+ and then execute the following commands (cut and paste from
+ here):
+ -- add builtin functions that are new to 1.01
+
+ create function int4eqoid (int4, oid) returns bool as 'foo'
+ language 'internal';
+ create function oideqint4 (oid, int4) returns bool as 'foo'
+ language 'internal';
+ create function char2icregexeq (char2, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char2icregexne (char2, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char4icregexeq (char4, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char4icregexne (char4, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char8icregexeq (char8, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char8icregexne (char8, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char16icregexeq (char16, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function char16icregexne (char16, text) returns bool as
+ 'foo'
+ language 'internal';
+ create function texticregexeq (text, text) returns bool as 'foo'
+ language 'internal';
+ create function texticregexne (text, text) returns bool as 'foo'
+ language 'internal';
+
+ -- add builtin functions that are new to 1.01
+
+ create operator = (leftarg = int4, rightarg = oid, procedure =
+ int4eqoid);
+ create operator = (leftarg = oid, rightarg = int4, procedure =
+ oideqint4);
+ create operator ~* (leftarg = char2, rightarg = text, procedure =
+ char2icregexeq);
+ create operator !~* (leftarg = char2, rightarg = text, procedure
+ = char2icregexne);
+ create operator ~* (leftarg = char4, rightarg = text, procedure =
+ char4icregexeq);
+ create operator !~* (leftarg = char4, rightarg = text, procedure
+ = char4icregexne);
+ create operator ~* (leftarg = char8, rightarg = text, procedure =
+ char8icregexeq);
+ create operator !~* (leftarg = char8, rightarg = text, procedure
+ = char8icregexne);
+ create operator ~* (leftarg = char16, rightarg = text, procedure
+ = char16icregexeq);
+ create operator !~* (leftarg = char16, rightarg = text, procedure
+ = char16icregexne);
+ create operator ~* (leftarg = text, rightarg = text, procedure =
+ texticregexeq);
+ create operator !~* (leftarg = text, rightarg = text, procedure =
+ texticregexne);
Detailed Change List
Incompatibilities:
- * 1.01 is backwards compatible with 1.0 database provided the user
- follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file.
- If those steps are not taken, 1.01 is not compatible with 1.0
+ * 1.01 is backwards compatible with 1.0 database provided the user
+ follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file.
+ If those steps are not taken, 1.01 is not compatible with 1.0
database.
Enhancements:
- * added PQdisplayTuples() to libpq and changed monitor and psql to
+ * added PQdisplayTuples() to libpq and changed monitor and psql to
use it
- * added NeXT port (requires SysVIPC implementation)
- * added CAST .. AS ... syntax
- * added ASC and DESC keywords
- * added 'internal' as a possible language for CREATE FUNCTION
- internal functions are C functions which have been statically
+ * added NeXT port (requires SysVIPC implementation)
+ * added CAST .. AS ... syntax
+ * added ASC and DESC keywords
+ * added 'internal' as a possible language for CREATE FUNCTION
+ internal functions are C functions which have been statically
linked
- into the postgres backend.
- * a new type "name" has been added for system identifiers (table
+ into the postgres backend.
+ * a new type "name" has been added for system identifiers (table
names,
- attribute names, etc.) This replaces the old char16 type. The
- of name is set by the NAMEDATALEN #define in src/Makefile.global
- * a readable reference manual that describes the query language.
- * added host-based access control. A configuration file
+ attribute names, etc.) This replaces the old char16 type. The
+ of name is set by the NAMEDATALEN #define in src/Makefile.global
+ * a readable reference manual that describes the query language.
+ * added host-based access control. A configuration file
($PGDATA/pg_hba)
- is used to hold the configuration data. If host-based access
+ is used to hold the configuration data. If host-based access
control
- is not desired, comment out HBA=1 in src/Makefile.global.
- * changed regex handling to be uniform use of Henry Spencer's regex
+ is not desired, comment out HBA=1 in src/Makefile.global.
+ * changed regex handling to be uniform use of Henry Spencer's regex
code
- regardless of platform. The regex code is included in the
+ regardless of platform. The regex code is included in the
distribution
- * added functions and operators for case-insensitive regular
+ * added functions and operators for case-insensitive regular
expressions.
- The operators are ~* and !~*.
- * pg_dump uses COPY instead of SELECT loop for better performance
+ The operators are ~* and !~*.
+ * pg_dump uses COPY instead of SELECT loop for better performance
Bug fixes:
- * fixed an optimizer bug that was causing core dumps when
- functions calls were used in comparisons in the WHERE clause
- * changed all uses of getuid to geteuid so that effective uids are
+ * fixed an optimizer bug that was causing core dumps when
+ functions calls were used in comparisons in the WHERE clause
+ * changed all uses of getuid to geteuid so that effective uids are
used
- * psql now returns non-zero status on errors when using -c
- * applied public patches 1-14
+ * psql now returns non-zero status on errors when using -c
+ * applied public patches 1-14
Release v1.0
Detailed Change List
Copyright change:
- * The copyright of Postgres 1.0 has been loosened to be freely
+ * The copyright of Postgres 1.0 has been loosened to be freely
modifiable
- and modifiable for any purpose. Please read the COPYRIGHT file.
- Thanks to Professor Michael Stonebraker for making this possible.
+ and modifiable for any purpose. Please read the COPYRIGHT file.
+ Thanks to Professor Michael Stonebraker for making this possible.
Incompatibilities:
- * date formats have to be MM-DD-YYYY (or DD-MM-YYYY if you're
+ * date formats have to be MM-DD-YYYY (or DD-MM-YYYY if you're
using
- EUROPEAN STYLE). This follows SQL-92 specs.
- * "delimiters" is now a keyword
+ EUROPEAN STYLE). This follows SQL-92 specs.
+ * "delimiters" is now a keyword
Enhancements:
- * sql LIKE syntax has been added
- * copy command now takes an optional USING DELIMITER
+ * sql LIKE syntax has been added
+ * copy command now takes an optional USING DELIMITER
specification.
- delimiters can be any single-character string.
- * IRIX 5.3 port has been added.
- Thanks to Paul Walmsley and others.
- * updated pg_dump to work with new libpq
- * \d has been added psql
- Thanks to Keith Parks
- * regexp performance for architectures that use POSIX regex has
+ delimiters can be any single-character string.
+ * IRIX 5.3 port has been added.
+ Thanks to Paul Walmsley and others.
+ * updated pg_dump to work with new libpq
+ * \d has been added psql
+ Thanks to Keith Parks
+ * regexp performance for architectures that use POSIX regex has
been
- improved due to caching of precompiled patterns.
- Thanks to Alistair Crooks
- * a new version of libpq++
- Thanks to William Wanders
+ improved due to caching of precompiled patterns.
+ Thanks to Alistair Crooks
+ * a new version of libpq++
+ Thanks to William Wanders
Bug fixes:
- * arbitrary userids can be specified in the createuser script
- * \c to connect to other databases in psql now works.
- * bad pg_proc entry for float4inc() is fixed
- * users with usecreatedb field set can now create databases
+ * arbitrary userids can be specified in the createuser script
+ * \c to connect to other databases in psql now works.
+ * bad pg_proc entry for float4inc() is fixed
+ * users with usecreatedb field set can now create databases
without
- having to be usesuper
- * remove access control entries when the entry no longer has any
- permissions
- * fixed non-portable datetimes implementation
- * added kerberos flags to the src/backend/Makefile
- * libpq now works with kerberos
- * typographic errors in the user manual have been corrected.
- * btrees with multiple index never worked, now we tell you they
+ having to be usesuper
+ * remove access control entries when the entry no longer has any
+ permissions
+ * fixed non-portable datetimes implementation
+ * added kerberos flags to the src/backend/Makefile
+ * libpq now works with kerberos
+ * typographic errors in the user manual have been corrected.
+ * btrees with multiple index never worked, now we tell you they
don't
- work when you try to use them
+ work when you try to use them
Postgres95 Beta 0.03
Detailed Change List
Incompatible changes:
- * BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS
+ * BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS
VERSIONS
- (due to system catalog changes and indexing structure changes).
- * double-quote (") is deprecated as a quoting character for string
+ (due to system catalog changes and indexing structure changes).
+ * double-quote (") is deprecated as a quoting character for string
literals;
- you need to convert them to single quotes (').
- * name of aggregates (eg. int4sum) are renamed in accordance with
+ you need to convert them to single quotes (').
+ * name of aggregates (eg. int4sum) are renamed in accordance with
the
- SQL standard (eg. sum).
- * CHANGE ACL syntax is replaced by GRANT/REVOKE syntax.
- * float literals (eg. 3.14) are now of type float4 (instead of
+ SQL standard (eg. sum).
+ * CHANGE ACL syntax is replaced by GRANT/REVOKE syntax.
+ * float literals (eg. 3.14) are now of type float4 (instead of
float8 in
- previous releases); you might have to do typecasting if you
+ previous releases); you might have to do typecasting if you
depend on it
- being of type float8. If you neglect to do the typecasting and
+ being of type float8. If you neglect to do the typecasting and
you assign
- a float literal to a field of type float8, you may get incorrect
+ a float literal to a field of type float8, you may get incorrect
values
- stored!
- * LIBPQ has been totally revamped so that frontend applications
- can connect to multiple backends
- * the usesysid field in pg_user has been changed from int2 to int4
+ stored!
+ * LIBPQ has been totally revamped so that frontend applications
+ can connect to multiple backends
+ * the usesysid field in pg_user has been changed from int2 to int4
to
- allow wider range of Unix user ids.
- * the netbsd/freebsd/bsd o/s ports have been consolidated into a
- single BSD44_derived port. (thanks to Alistair Crooks)
+ allow wider range of Unix user ids.
+ * the netbsd/freebsd/bsd o/s ports have been consolidated into a
+ single BSD44_derived port. (thanks to Alistair Crooks)
SQL standard-compliance (the following details changes that makes
postgres95
more compliant to the SQL-92 standard):
- * the following SQL types are now built-in: smallint, int(eger),
+ * the following SQL types are now built-in: smallint, int(eger),
float, real,
- char(N), varchar(N), date and time.
+ char(N), varchar(N), date and time.
- The following are aliases to existing postgres types:
- smallint -> int2
- integer, int -> int4
- float, real -> float4
- char(N) and varchar(N) are implemented as truncated text types.
+ The following are aliases to existing postgres types:
+ smallint -> int2
+ integer, int -> int4
+ float, real -> float4
+ char(N) and varchar(N) are implemented as truncated text types.
In
- addition, char(N) does blank-padding.
- * single-quote (') is used for quoting string literals; '' (in
+ addition, char(N) does blank-padding.
+ * single-quote (') is used for quoting string literals; '' (in
addition to
- \') is supported as means of inserting a single quote in a string
- * SQL standard aggregate names (MAX, MIN, AVG, SUM, COUNT) are used
- (Also, aggregates can now be overloaded, i.e. you can define your
- own MAX aggregate to take in a user-defined type.)
- * CHANGE ACL removed. GRANT/REVOKE syntax added.
- - Privileges can be given to a group using the "GROUP" keyword.
- For example:
- GRANT SELECT ON foobar TO GROUP my_group;
- The keyword 'PUBLIC' is also supported to mean all users.
-
- Privileges can only be granted or revoked to one user or
+ \') is supported as means of inserting a single quote in a string
+ * SQL standard aggregate names (MAX, MIN, AVG, SUM, COUNT) are used
+ (Also, aggregates can now be overloaded, i.e. you can define your
+ own MAX aggregate to take in a user-defined type.)
+ * CHANGE ACL removed. GRANT/REVOKE syntax added.
+ - Privileges can be given to a group using the "GROUP" keyword.
+ For example:
+ GRANT SELECT ON foobar TO GROUP my_group;
+ The keyword 'PUBLIC' is also supported to mean all users.
+
+ Privileges can only be granted or revoked to one user or
group
- at a time.
+ at a time.
- "WITH GRANT OPTION" is not supported. Only class owners can
+ "WITH GRANT OPTION" is not supported. Only class owners can
change
- access control
- - The default access control is to to grant users readonly
+ access control
+ - The default access control is to to grant users readonly
access.
- You must explicitly grant insert/update access to users. To
+ You must explicitly grant insert/update access to users. To
change
- this, modify the line in
- src/backend/utils/acl.h
- that defines ACL_WORLD_DEFAULT
+ this, modify the line in
+ src/backend/utils/acl.h
+ that defines ACL_WORLD_DEFAULT
Bug fixes:
- * the bug where aggregates of empty tables were not run has been
+ * the bug where aggregates of empty tables were not run has been
fixed. Now,
- aggregates run on empty tables will return the initial conditions
+ aggregates run on empty tables will return the initial conditions
of the
- aggregates. Thus, COUNT of an empty table will now properly
+ aggregates. Thus, COUNT of an empty table will now properly
return 0.
- MAX/MIN of an empty table will return a tuple of value NULL.
- * allow the use of \; inside the monitor
- * the LISTEN/NOTIFY asynchronous notification mechanism now work
- * NOTIFY in rule action bodies now work
- * hash indices work, and access methods in general should perform
+ MAX/MIN of an empty table will return a tuple of value NULL.
+ * allow the use of \; inside the monitor
+ * the LISTEN/NOTIFY asynchronous notification mechanism now work
+ * NOTIFY in rule action bodies now work
+ * hash indices work, and access methods in general should perform
better.
- creation of large btree indices should be much faster. (thanks
+ creation of large btree indices should be much faster. (thanks
to Paul
- Aoki)
+ Aoki)
Other changes and enhancements:
- * addition of an EXPLAIN statement used for explaining the query
+ * addition of an EXPLAIN statement used for explaining the query
execution
- plan (eg. "EXPLAIN SELECT * FROM EMP" prints out the execution
+ plan (eg. "EXPLAIN SELECT * FROM EMP" prints out the execution
plan for
- the query).
- * WARN and NOTICE messages no longer have timestamps on them. To
+ the query).
+ * WARN and NOTICE messages no longer have timestamps on them. To
turn on
- timestamps of error messages, uncomment the line in
- src/backend/utils/elog.h:
- /* define ELOG_TIMESTAMPS */
- * On an access control violation, the message
- "Either no such class or insufficient privilege"
- will be given. This is the same message that is returned when
- a class is not found. This dissuades non-privileged users from
- guessing the existence of privileged classes.
- * some additional system catalog changes have been made that are
+ timestamps of error messages, uncomment the line in
+ src/backend/utils/elog.h:
+ /* define ELOG_TIMESTAMPS */
+ * On an access control violation, the message
+ "Either no such class or insufficient privilege"
+ will be given. This is the same message that is returned when
+ a class is not found. This dissuades non-privileged users from
+ guessing the existence of privileged classes.
+ * some additional system catalog changes have been made that are
not
- visible to the user.
+ visible to the user.
libpgtcl changes:
- * The -oid option has been added to the "pg_result" tcl command.
- pg_result -oid returns oid of the last tuple inserted. If the
- last command was not an INSERT, then pg_result -oid returns "".
- * the large object interface is available as pg_lo* tcl commands:
- pg_lo_open, pg_lo_close, pg_lo_creat, etc.
+ * The -oid option has been added to the "pg_result" tcl command.
+ pg_result -oid returns oid of the last tuple inserted. If the
+ last command was not an INSERT, then pg_result -oid returns "".
+ * the large object interface is available as pg_lo* tcl commands:
+ pg_lo_open, pg_lo_close, pg_lo_creat, etc.
Portability enhancements and New Ports:
- * flex/lex problems have been cleared up. Now, you should be able
+ * flex/lex problems have been cleared up. Now, you should be able
to use
- flex instead of lex on any platforms. We no longer make
+ flex instead of lex on any platforms. We no longer make
assumptions of
- what lexer you use based on the platform you use.
- * The Linux-ELF port is now supported. Various configuration have
+ what lexer you use based on the platform you use.
+ * The Linux-ELF port is now supported. Various configuration have
been
- tested: The following configuration is known to work:
- kernel 1.2.10, gcc 2.6.3, libc 4.7.2, flex 2.5.2, bison 1.24
- with everything in ELF format,
+ tested: The following configuration is known to work:
+ kernel 1.2.10, gcc 2.6.3, libc 4.7.2, flex 2.5.2, bison 1.24
+ with everything in ELF format,
New utilities:
- * ipcclean added to the distribution
- ipcclean usually does not need to be run, but if your backend
+ * ipcclean added to the distribution
+ ipcclean usually does not need to be run, but if your backend
crashes
- and leaves shared memory segments hanging around, ipcclean will
- clean them up for you.
+ and leaves shared memory segments hanging around, ipcclean will
+ clean them up for you.
New documentation:
- * the user manual has been revised and libpq documentation added.
+ * the user manual has been revised and libpq documentation added.
Postgres95 Beta 0.02
Detailed Change List
Incompatible changes:
- * The SQL statement for creating a database is 'CREATE DATABASE'
+ * The SQL statement for creating a database is 'CREATE DATABASE'
instead
- of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE'
+ of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE'
instead
- of 'DESTROYDB'. However, the names of the executables 'createdb'
+ of 'DESTROYDB'. However, the names of the executables 'createdb'
and
- 'destroydb' remain the same.
-
+ 'destroydb' remain the same.
+
New tools:
- * pgperl - a Perl (4.036) interface to Postgres95
- * pg_dump - a utility for dumping out a postgres database into a
- script file containing query commands. The script files are
+ * pgperl - a Perl (4.036) interface to Postgres95
+ * pg_dump - a utility for dumping out a postgres database into a
+ script file containing query commands. The script files are
in a ASCII
- format and can be used to reconstruct the database, even on
+ format and can be used to reconstruct the database, even on
other
- machines and other architectures. (Also good for converting
- a Postgres 4.2 database to Postgres95 database.)
+ machines and other architectures. (Also good for converting
+ a Postgres 4.2 database to Postgres95 database.)
The following ports have been incorporated into
postgres95-beta-0.02:
- * the NetBSD port by Alistair Crooks
- * the AIX port by Mike Tung
- * the Windows NT port by Jon Forrest (more stuff but not done yet)
- * the Linux ELF port by Brian Gallew
+ * the NetBSD port by Alistair Crooks
+ * the AIX port by Mike Tung
+ * the Windows NT port by Jon Forrest (more stuff but not done yet)
+ * the Linux ELF port by Brian Gallew
The following bugs have been fixed in postgres95-beta-0.02:
- * new lines not escaped in COPY OUT and problem with COPY OUT when
+ * new lines not escaped in COPY OUT and problem with COPY OUT when
first
- attribute is a '.'
- * cannot type return to use the default user id in createuser
- * SELECT DISTINCT on big tables crashes
- * Linux installation problems
- * monitor doesn't allow use of 'localhost' as PGHOST
- * psql core dumps when doing \c or \l
- * the "pgtclsh" target missing from src/bin/pgtclsh/Makefile
- * libpgtcl has a hard-wired default port number
- * SELECT DISTINCT INTO TABLE hangs
- * CREATE TYPE doesn't accept 'variable' as the internallength
- * wrong result using more than 1 aggregate in a SELECT
+ attribute is a '.'
+ * cannot type return to use the default user id in createuser
+ * SELECT DISTINCT on big tables crashes
+ * Linux installation problems
+ * monitor doesn't allow use of 'localhost' as PGHOST
+ * psql core dumps when doing \c or \l
+ * the "pgtclsh" target missing from src/bin/pgtclsh/Makefile
+ * libpgtcl has a hard-wired default port number
+ * SELECT DISTINCT INTO TABLE hangs
+ * CREATE TYPE doesn't accept 'variable' as the internallength
+ * wrong result using more than 1 aggregate in a SELECT
Postgres95 Beta 0.01
-PostgreSQL Installation Guide
-by The PostgreSQL Development Team
+Chapter 0. Installation
-PostgreSQL is © 1998-9 by the Postgres Global Development Group.
Table of Contents
+Requirements to Run Postgres
+Installation Procedure
+Playing with Postgres
+The Next Step
+Porting Notes
+
+ Complete installation instructions for Postgres v6.5.3.
+
+Before installing Postgres, you may wish to visit www.postgresql.org for up
+to date information, patches, etc.
+
+These installation instructions assume:
+
+ * Commands are Unix-compatible. See note below.
+
+ * Defaults are used except where noted.
- Summary
- 1. Introduction
- 2. Ports
- Currently Supported Platforms
- Unsupported Platforms
- 3. Installation
- Requirements to Run Postgres
- Installation Procedure
- Playing with Postgres
- The Next Step
- Porting Notes
- 4. Configuration Options
- Parameters for Configuration (configure)
- Parameters for Building (make)
- Locale Support
- What are the Benefits?
- What are the Drawbacks?
- Kerberos Authentication
- Availability
- Installation
- Operation
- 5. Release Notes
- Release 6.5.1
- Migration to v6.5.1
- Detailed Change List
- Release 6.5
- Migration to v6.5
- Multi-Version Concurrency Control
- Detailed Change List
-
-Summary
-
- Postgres, developed originally in the UC Berkeley
- Computer Science Department, pioneered many of the
- object-relational concepts now becoming available in
- some commercial databases. It provides SQL92/SQL3
- language support, transaction integrity, and type
- extensibility. PostgreSQL is a public-domain, open
- source descendant of this original Berkeley code.
-
-Chapter 1. Introduction
-
- This installation procedure makes some assumptions
- about the desired configuration and runtime
- environment for your system. This may be adequate for
- many installations, and is almost certainly adequate
- for a first installation. But you may want to do an
- initial installation up to the point of unpacking the
- source tree and installing documentation, and then
- print or browse the Administrator's Guide.
-
-Chapter 2. Ports
-
- This manual describes version 6.5.1 of Postgres. The
- Postgres developer community has compiled and tested
- Postgres on a number of platforms. Check the web site
- (http://www.postgresql.org/docs/admin/ports.htm) for
- the latest information.
-
-Currently Supported Platforms
-
- At the time of publication, the following platforms
- have been tested:
-
- Table 2-1. Supported Platforms
- OS Processor Version Reported Remarks
- AIX 4.3.2 RS6000 v6.5 1999-05-26 (Andreas Zeugswetter
- (mailto:Andreas.Zeugswetter@telecom.at))
- BSDI x86 v6.5 1999-05-25 (Bruce Momjian
- (mailto:maillist@candle.pha.pa.us)
- FreeBSD x86 v6.5 1999-05-25 (Tatsuo Ishii
- 2.2.x-4.0 (mailto:t-ishii@sra.co.jp),
- Marc Fournier
- (mailto:scrappy@hub.org))
- DGUX m88k v6.3 1998-03-01 v6.4 probably OK.
- 5.4R4.11 Needs new maintainer.
- (Brian E Gallew
- (mailto:geek+@cmu.edu))
- Digital Alpha v6.4 1998-10-29 Minor patchable problems
- Unix 4.0 (Pedro J. Lobo
- (mailto:pjlobo@euitt.upm.es))
- HPUX PA-RISC v6.4 1998-10-25 Both 9.0x and 10.20
- (Tom Lane (mailto:tgl@sss.pgh.pa.us),
- Stan Brown (mailto:stanb@awod.com))
- IRIX 6.5 MIPS v6.4 1998-12-29 IRIX 5.x is different
- (Mark Dalphin (mdalphin@amgen.com))
- linux Alpha v6.3.2 1998-04-16 Mostly successful. Needs
- 2.0.x work for v6.4.
- (Ryan Kirkpatrick
- (mailto:rkirkpat@nag.cs.colorado.edu))
- linux x86 v6.4 1998-10-27 (Thomas Lockhart
- 2.0.x/libc5 (mailto:lockhart@alumni.caltech.edu))
- linux x86 v6.4 1999-05-24 (Thomas Lockhart
- 2.0.x/glibc2 (mailto:lockhart@alumni.caltech.edu))
- linux MIPS v6.4 1998-12-16 Cobalt Qube (Tatsuo Ishii
- 2.0.x (mailto:t-ishii@sra.co.jp))
- linux Sparc v6.4 1998-10-25 (Tom Szybist
- 2.0.x (mailto:szybist@boxhill.com))
- linuxPPC PPC603e v6.4 1998-10-26 Powerbook 2400c
- 2.1.24 (Tatsuo Ishii
- (mailto:t-ishii@sra.co.jp))
- mklinux PPC750 v6.4 1998-09-16 PowerMac 7600
- DR3 (Tatsuo Ishii
- (mailto:t-ishii@sra.co.jp))
- NetBSD arm32 v6.5 1999-04-14 (Andrew McMurry
- (mailto:a.mcmurry1@physics.oxford.ac.uk))
- NetBSD/i3- x86 v6.4 1998-10-25 (Brook Milligan
- 86 1.3.2 (mailto:brook@trillium.NMSU.Edu))
- NetBSD m68k v6.4.2 1998-12-28 Mac SE/30 (Mr. Mutsuki
- Nakajima, Tatsuo Ishii
- (mailto:t-ishii@sra.co.jp))
- NetBSD- NS32532 v6.4 1998-10-27 small problems
- current in date/time math (Jon Buller
- (mailto:jonb@metronet.com))
- NetBSD/sp- Sparc v6.4 1998-10-27 (Tom I Helbekkmo
- arc 1.3H (mailto:tih@hamartun.priv.no))
- NetBSD 1.3 VAX v6.3 1998-03-01 (Tom I Helbekkmo
- (mailto:tih@hamartun.priv.no))
- SCO x86 v6.5 1999-05-25 (Andrew Merrill
- OpenServer 5 (mailto:andrew@compclass.com))
- SCO x86 v6.5 1999-05-25 (Andrew Merrill
- UnixWare 7 (mailto:andrew@compclass.com))
- Solaris x86 v6.4 1998-10-28 (Marc Fournier
- (mailto:scrappy@hub.org))
- Solaris Sparc v6.4 1998-10-28 (Tom Szybist
- 2.6-2.7 (mailto:szybist@boxhill.com),
- Frank Ridderbusch
- (mailto:ridderbusch.pad@sni.de))
- SunOS Sparc v6.3 1998-03-01 Patches submitted
- 4.1.4 (Tatsuo Ishii
- (mailto:t-ishii@sra.co.jp))
- SVR4 MIPS v6.4 1998-10-28 No 64-bit int compiler
- support (Frank Ridderbusch
- (mailto:ridderbusch.pad@sni.de))
- Windows x86 v6.4 1999-01-06 Client-side libraries
- or ODBC/JDBC. No server yet.
- (Magnus Hagander
- (mha@sollentuna.net)
- Windows NT x86 v6.5 1999-05-26 Working with the Cygwin
- library. (Daniel Horak
- (mailto:Dan.Horak@email.cz))
-
-
-
- Platforms listed for v6.3.x and v6.4.x should also
- work with v6.5.1, but we did not receive explicit
- confirmation of such at the time this list was
- compiled.
-
- Note: For Windows NT, the server-side port of
- Postgres has recently been accomplished. The
- Cygnus library is required to compile it.
-
-Unsupported Platforms
-
- There are a few platforms which have been attempted
- and which have been reported to not work with the
- standard distribution. Others listed here do not
- provide sufficient library support for an attempt.
-
- Table 2-2. Possibly Incompatible Platforms
- OS Processor Version Reported Remarks
- MacOS all v6.3 1998-03-01 Not library compatible;
- use ODBC/JDBC
- NextStep x86 v6.x 1998-03-01 Client-only support;
- v1.0.9 worked with patches
- (David Wetzel
- (mailto:dave@turbocat.de))
- SVR4 4.4 m88k v6.2.1 1998-03-01 Confirmed
- with patching;
- v6.4.x will need TAS
- spinlock code (Doug
- Winterburn
- (mailto:dlw@seavme.xroads.com))
- Ultrix MIPS,VAX? v6.x 1998-03-01 No recent reports;
- obsolete?
-
-
-Chapter 3. Installation
-
- Complete installation instructions for Postgres
- v6.5.1.
-
- Before installing Postgres, you may wish to visit
- www.postgresql.org (http://www.postgresql.org) for up
- to date information, patches, etc.
- These installation instructions assume:
- o Commands are Unix-compatible. See note below.
- o Defaults are used except where noted.
- o User postgres is the Postgres superuser.
- o The source path is /usr/src/pgsql (other paths are
- possible).
- o The runtime path is /usr/local/pgsql (other paths
- are possible).
-
- Commands were tested on RedHat Linux version 5.2
- using the tcsh shell. Except where noted, they will
- probably work on most systems. Commands like ps and
- tar may vary wildly between platforms on what options
- you should use. Use common sense before typing in
- these commands.
- Our Makefiles require GNU make (called ?gmake? in this
- document). They will not work with non-GNU make
- programs. If you have GNU make installed under the
- name ?make? instead of ?gmake?, then you will use the
- command make instead. That's OK, but you need to have
- the GNU form of make to succeed with an installation.
+ * User postgres is the Postgres superuser.
+
+ * The source path is /usr/src/pgsql (other paths are possible).
+
+ * The runtime path is /usr/local/pgsql (other paths are possible).
+
+Commands were tested on RedHat Linux version 5.2 using the tcsh shell.
+Except where noted, they will probably work on most systems. Commands like
+ps and tar may vary wildly between platforms on what options you should use.
+Use common sense before typing in these commands.
+
+Our Makefiles require GNU make (called "gmake" in this document). They will
+not work with non-GNU make programs. If you have GNU make installed under
+the name "make" instead of "gmake", then you will use the command make
+instead. That's OK, but you need to have the GNU form of make to succeed
+with an installation.
Requirements to Run Postgres
- Up to date information on supported platforms is at
- http://www.postgresql.org/docs/admin/install.htm
- (http://www.postgresql.org/docs/admin/install.htm).
- In general, most Unix-compatible platforms with
- modern libraries should be able to run Postgres.
- Although the minimum required memory for running
- Postgres is as little as 8MB, there are noticable
- improvements in runtimes for the regression tests
- when expanding memory up to 96MB on a relatively fast
- dual-processor system running X-Windows. The rule is
- you can never have too much memory.
- Check that you have sufficient disk space. You will
- need about 30 Mbytes for /usr/src/pgsql, about 5
- Mbytes for /usr/local/pgsql (excluding your database)
- and 1 Mbyte for an empty database. The database will
- temporarily grow to about 20 Mbytes during the
- regression tests. You will also need about 3 Mbytes
- for the distribution tar file.
- We therefore recommend that during installation and
- testing you have well over 20 Mbytes free under
- /usr/local and another 25 Mbytes free on the disk
- partition containing your database. Once you delete
- the source files, tar file and regression database,
- you will need 2 Mbytes for /usr/local/pgsql, 1 Mbyte
- for the empty database, plus about five times the
- space you would require to store your database data
- in a flat file.
- To check for disk space, use
-
- $ df -k
-
-
-
+Up to date information on supported platforms is at
+http://www.postgresql.org/docs/admin/install.htm. In general, most
+Unix-compatible platforms with modern libraries should be able to run
+Postgres.
+
+Although the minimum required memory for running Postgres is as little as
+8MB, there are noticable improvements in runtimes for the regression tests
+when expanding memory up to 96MB on a relatively fast dual-processor system
+running X-Windows. The rule is you can never have too much memory.
+
+Check that you have sufficient disk space. You will need about 30 Mbytes for
+/usr/src/pgsql, about 5 Mbytes for /usr/local/pgsql (excluding your
+database) and 1 Mbyte for an empty database. The database will temporarily
+grow to about 20 Mbytes during the regression tests. You will also need
+about 3 Mbytes for the distribution tar file.
+
+We therefore recommend that during installation and testing you have well
+over 20 Mbytes free under /usr/local and another 25 Mbytes free on the disk
+partition containing your database. Once you delete the source files, tar
+file and regression database, you will need 2 Mbytes for /usr/local/pgsql, 1
+Mbyte for the empty database, plus about five times the space you would
+require to store your database data in a flat file.
+
+To check for disk space, use
+
+$ df -k
+
+
+ ------------------------------------------------------------------------
Installation Procedure
- Postgres Installation
- For a fresh install or upgrading from previous
- releases of Postgres:
- 1. Read any last minute information and platform
- specific porting notes. There are some platform
- specific notes at the end of this file for
- Ultrix4.x, Linux, BSD/OS and NeXT. There are other
- files in directory /usr/src/pgsql/doc, including
- files FAQ-Irix and FAQ-Linux. Also look in
- directory ftp://ftp.postgresql.org/pub. If there
- is a file called INSTALL in this directory then
- this file will contain the latest installation
- information.
- Please note that a "tested" platform in the list
- given earlier simply means that someone went to
- the effort at some point of making sure that a
- Postgres distribution would compile and run on
- this platform without modifying the code. Since
- the current developers will not have access to all
- of these platforms, some of them may not compile
- cleanly and pass the regression tests in the
- current release due to minor problems. Any such
- known problems and their solutions will be posted
- in ftp://ftp.postgresql.org/pub/INSTALL.
- 2. Create the Postgres superuser account (postgres is
- commonly used) if it does not already exist.
- The owner of the Postgres files can be any
- unprivileged user account. It must not be root,
- bin, or any other account with special access
- rights, as that would create a security risk.
- 3. Log in to the Postgres superuser account. Most of
- the remaining steps in the installation will
- happen in this account.
- 4. Ftp file
- ftp://ftp.postgresql.org/pub/postgresql-v6.5.1.tar.gz
- from the Internet. Store it in your home
- directory.
- 5. Some platforms use flex. If your system uses flex
- then make sure you have a good version. To check,
- type
- $ flex --version
- If the flex command is not found then you
- probably do not need it. If the version is 2.5.2
- or 2.5.4 or greater then you are okay. If it is
- 2.5.3 or before 2.5.2 then you will have to
- upgrade flex. You may get it at
- ftp://prep.ai.mit.edu/pub/gnu/flex-2.5.4.tar.gz.
- If you need flex and don't have it or have the
- wrong version, then you will be told so when you
- attempt to compile the program. Feel free to skip
- this step if you aren't sure you need it. If you
- do need it then you will be told to
- install/upgrade flex when you try to compile
- Postgres.
- You may want to do the entire flex installation
- from the root account, though that is not
- absolutely necessary. Assuming that you want the
- installation to place files in the usual default
- areas, type the following:
- $ su -
- $ cd /usr/local/src
- ftp prep.ai.mit.edu
- ftp> cd /pub/gnu/
- ftp> binary
- ftp> get flex-2.5.4.tar.gz
- ftp> quit
- $ gunzip -c flex-2.5.4.tar.gz | tar xvf -
- $ cd flex-2.5.4
- $ configure --prefix=/usr
- $ gmake
- $ gmake check
- # You must be root when typing the next line:
- $ gmake install
- $ cd /usr/local/src
- $ rm -rf flex-2.5.4
- This will update files /usr/man/man1/flex.1,
- /usr/bin/flex, /usr/lib/libfl.a,
- /usr/include/FlexLexer.h and will add a link
- /usr/bin/flex++ which points to flex.
- 6. If you are not upgrading an existing system then
- skip to step 9. If you are upgrading from 6.5, you
- do not need to dump/reload or initdb. Simply
- compile the source code, stop the postmaster, do a
- "make install", and restart the postmaster.
- If you are upgrading from 6.4.* or earlier,
- back up your database. For alpha- and
- beta-level releases, the database format is liable
- to change, often every few weeks, with no notice
- besides a quick comment in the HACKERS mailing
- list. Full releases always require a dump/reload
- from previous releases. It is therefore a bad idea
- to skip this step.
-
- Tip: Do not use the pg_dumpall script from v6.0
- or everything will be owned by the Postgres
- super user.
-
- To dump your fairly recent post-v6.0 database
- installation, type
- $ pg_dumpall > db.out
- To use the latest pg_dumpall script on your
- existing older database before upgrading Postgres,
- pull the most recent version of pg_dumpall from
- the new distribution:
- $ cd
- $ gunzip -c postgresql-v6.5.1.tar.gz \
- | tar xvf - src/bin/pg_dump/pg_dumpall
- $ chmod a+x src/bin/pg_dump/pg_dumpall
- $ src/bin/pg_dump/pg_dumpall > db.out
- $ rm -rf src
- If you wish to preserve object id's (oids), then
- use the -o option when running pg_dumpall.
- However, unless you have a special reason for
- doing this (such as using OIDs as keys in tables),
- don't do it.
- If the pg_dumpall command seems to take a long
- time and you think it might have died, then, from
- another terminal, type
- $ ls -l db.out
- several times to see if the size of the file is
- growing.
- Please note that if you are upgrading from a
- version prior to Postgres95 v1.09 then you must
- back up your database, install Postgres95 v1.09,
- restore your database, then back it up again. You
- should also read the release notes which should
- cover any release-specific issues.
-
- Caution
- You must make sure that your database is not
- updated in the middle of your backup. If
- necessary, bring down postmaster, edit the
- permissions in file
- /usr/local/pgsql/data/pg_hba.conf to allow
- only you on, then bring postmaster back up.
-
-
-
- 7. If you are upgrading an existing system then kill
- the postmaster. Type
- $ ps -ax | grep postmaster
- This should list the process numbers for a number
- of processes. Type the following line, with pid
- replaced by the process id for process postmaster.
- (Do not use the id for process "grep postmaster".)
- Type
- $ kill pid
- to actually stop the process.
-
- Tip: On systems which have Postgres started at
- boot time, there is probably a startup file
- which will accomplish the same thing. For
- example, on my Linux system I can type
- $ /etc/rc.d/init.d/postgres.init stop
- to halt Postgres.
-
- 8. If you are upgrading an existing system then move
- the old directories out of the way. If you are
- short of disk space then you may have to back up
- and delete the directories instead. If you do
- this, save the old database in the
- /usr/local/pgsql/data directory tree. At a
- minimum, save file
- /usr/local/pgsql/data/pg_hba.conf.
- Type the following:
- $ su -
- $ cd /usr/src
- $ mv pgsql pgsql_6_0
- $ cd /usr/local
- $ mv pgsql pgsql_6_0
- $ exit
- If you are not using /usr/local/pgsql/data as
- your data directory (check to see if environment
- variable PGDATA is set to something else) then you
- will also want to move this directory in the same
- manner.
- 9. Make new source and install directories. The
- actual paths can be different for your
- installation but you must be consistent throughout
- this procedure.
-
- Note: There are two places in this installation
- procedure where you will have an opportunity to
- specify installation locations for programs,
- libraries, documentation, and other files.
- Usually it is sufficient to specify these at the
- gmake install stage of installation.
-
- Type
- $ su
- $ cd /usr/src
- $ mkdir pgsql
- $ chown postgres:postgres pgsql
- $ cd /usr/local
- $ mkdir pgsql
- $ chown postgres:postgres pgsql
- $ exit
- 10. Unzip and untar the new source file. Type
- $ cd /usr/src/pgsql
- $ gunzip -c ~/postgresql-v6.5.1.tar.gz | tar xvf -
- 11. Configure the source code for your system. It
- is this step at which you can specify your actual
- installation path for the build process (see the
- --prefix option below). Type
- $ cd /usr/src/pgsql/src
- $ ./configure [ options ]
- a. Among other chores, the configure script
- selects a system-specific "template" file
- from the files provided in the template
- subdirectory. If it cannot guess which one to
- use for your system, it will say so and exit.
- In that case you'll need to figure out which
- one to use and run configure again, this time
- giving the --with-template=TEMPLATE option to
- make the right file be chosen.
-
- Please Report Problems: If your system is not
- automatically recognized by configure and
- you have to do this, please send email to
- scrappy@hub.org (mailto:scrappy@hub.org)
- with the output of the program
- ./config.guess. Indicate what the template
- file should be.
-
- b. Choose configuration options. Check
- Configuration Options for details. However,
- for a plain-vanilla first installation with
- no extra options like multi-byte character
- support or locale collation support it may be
- adequate to have chosen the installation
- areas and to run configure without extra
- options specified. The configure script
- accepts many additional options that you can
- use if you don't like the default
- configuration. To see them all, type
- ./configure --help
- Some of the more commonly used ones are:
- --prefix=BASEDIR Selects a different
- base directory for the
- installation of the
- Postgres configuration.
- The default is
- /usr/local/pgsql.
- --with-template=TEMPLATE
- Use template file
- TEMPLATE - the template
- files are assumed
- to be in the directory
- src/template, so
- look there for proper values.
- --with-tcl Build interface
- libraries and programs requiring
- Tcl/Tk, including
- libpgtcl, pgtclsh, and pgtksh.
- --with-perl Build the Perl
- interface library.
- --with-odbc Build the ODBC
- driver package.
- --enable-hba Enables Host Based
- Authentication (DEFAULT)
- --disable-hba Disables Host Based
- Authentication
- --enable-locale Enables USE_LOCALE
- --enable-cassert Enables
- ASSERT_CHECKING
- --with-CC=compiler
- Use a specific C
- compiler that the configure
- script cannot find.
- --with-CXX=compiler
- --without-CXX
- Use a specific C++
- compiler that the configure
- script cannot find,
- or exclude C++ compilation
- altogether. (This
- only affects libpq++ at
- present.)
- c. Here is the configure script used on a Sparc
- Solaris 2.5 system with /opt/postgres
- specified as the installation base directory:
- $ ./configure --prefix=/opt/postgres \
- --with-template=sparc_solaris-gcc
- --with-pgport=5432 \
- --enable-hba --disable-locale
-
- Tip: Of course, you may type these three
- lines all on the same line.
-
- 12. Install the man and HTML documentation. Type
- $ cd /usr/src/pgsql/doc
- $ gmake install
- The documentation is also available in Postscript
- format. Look for files ending with .ps.gz in the
- same directory.
- 13. Compile the program. Type
- $ cd /usr/src/pgsql/src
- $ gmake all >& make.log &
- $ tail -f make.log
- The last line displayed will hopefully be
- All of PostgreSQL is successfully made. Ready to
- install.
- Remember, ?gmake? may be called ?make? on your system.
- At this point, or earlier if you wish, type
- control-C to get out of tail. (If you have
- problems later on you may wish to examine file
- make.log for warning and error messages.)
-
- Note: You will probably find a number of warning
- messages in make.log. Unless you have problems
- later on, these messages may be safely ignored.
-
- If the compiler fails with a message stating that
- the flex command cannot be found then install flex
- as described earlier. Next, change directory back
- to this directory, type
- $ gmake clean
- then recompile again.
- Compiler options, such as optimization and
- debugging, may be specified on the command line
- using the COPT variable. For example, typing
- $ gmake COPT="-g" all >& make.log &
- would invoke your compiler's -g option in all
- steps of the build. See src/Makefile.global.in for
- further details.
- 14. Install the program. Type
- $ cd /usr/src/pgsql/src
- $ gmake install >& make.install.log &
- $ tail -f make.install.log
- The last line displayed will be
- gmake[1]: Leaving directory
- `/usr/src/pgsql/src/man'
- At this point, or earlier if you wish, type
- control-C to get out of tail. Remember, ?gmake? may
- be called ?make? on your system.
- 15. If necessary, tell your system how to find
- the new shared libraries. You can do one of the
- following, preferably the first:
- a. As root, edit file /etc/ld.so.conf. Add a
- line
- /usr/local/pgsql/lib
- to the file. Then run command /sbin/ldconfig.
- b. In a bash shell, type
- export
- LD_LIBRARY_PATH=/usr/local/pgsql/lib
- c. In a csh shell, type
- setenv LD_LIBRARY_PATH
- /usr/local/pgsql/lib
- Please note that the above commands may vary
- wildly for different operating systems. Check the
- platform specific notes, such as those for
- Ultrix4.x or and for non-ELF Linux.
- If, when you create the database, you get the
- message
- pg_id: can't load library 'libpq.so'
- then the above step was necessary. Simply do this
- step, then try to create the database again.
- 16. If you used the --with-perl option to
- configure, check the install log to see whether
- the Perl module was actually installed. If you've
- followed our advice to make the Postgres files be
- owned by an unprivileged userid, then the Perl
- module won't have been installed, for lack of
- write privileges on the Perl library directories.
- You can complete its installation, either now or
- later, by becoming the user that does own the Perl
- library (often root) (via su) and doing
- $ cd /usr/src/pgsql/src/interfaces/perl5
- $ gmake install
-
-
- 17. If it has not already been done, then prepare
- account postgres for using Postgres. Any account
- that will use Postgres must be similarly prepared.
- There are several ways to influence the runtime
- environment of the Postgres server. Refer to the
- Administrator's Guide for more information.
-
- Note: The following instructions are for a
- bash/sh shell. Adapt accordingly for other
- shells.
-
-
- a. Add the following lines to your login
- environment: shell, ~/.bash_profile:
- PATH=$PATH:/usr/local/pgsql/bin
- MANPATH=$MANPATH:/usr/local/pgsql/man
- PGLIB=/usr/local/pgsql/lib
- PGDATA=/usr/local/pgsql/data
- export PATH MANPATH PGLIB PGDATA
-
-
- b. Several regression tests could fail if the
- user's locale collation scheme is different
- from that of standard C locale.
- If you configure and compile Postgres with
- the --enable-locale option then set locale
- environment to C (or unset all LC_*
- variables) by putting these additional lines
- to your login environment before starting
- postmaster:
- LC_COLLATE=C
- LC_CTYPE=C
- LC_COLLATE=C
- export LC_COLLATE LC_CTYPE LC_COLLATE
-
-
-
-
-
- c. Make sure that you have defined these
- variables before continuing with the
- remaining steps. The easiest way to do this
- is to type:
- $ source ~/.bash_profile
-
-
- 18. Create the database installation from your
- Postgres superuser account (typically account
- postgres). Do not do the following as root! This
- would be a major security hole. Type
- $ initdb
- 19. Set up permissions to access the database
- system. Do this by editing file
- /usr/local/pgsql/data/pg_hba.conf. The
- instructions are included in the file. (If your
- database is not located in the default location,
- i.e. if PGDATA is set to point elsewhere, then the
- location of this file will change accordingly.)
- This file should be made read only again once you
- are finished. If you are upgrading from v6.0 or
- later you can copy file pg_hba.conf from your old
- database on top of the one in your new database,
- rather than redoing the file from scratch.
- 20. Briefly test that the backend will start and
- run by running it from the command line.
- a. Start the postmaster daemon running in the
- background by typing
- $ cd
- $ nohup postmaster -i > pgserver.log 2>&1 &
- b. Create a database by typing
- $ createdb
- c. Connect to the new database:
- $ psql
- d. And run a sample query:
- postgres=> SELECT datetime 'now';
- e. Exit psql:
- postgres=> \q
- f. Remove the test database (unless you will
- want to use it later for other tests):
- $ destroydb
- 21. Run postmaster in the background from your
- Postgres superuser account (typically account
- postgres). Do not run postmaster from the root
- account!
- Usually, you will want to modify your computer so
- that it will automatically start postmaster
- whenever it boots. It is not required; the
- Postgres server can be run successfully from
- non-privileged accounts without root intervention.
- Here are some suggestions on how to do this,
- contributed by various users.
- Whatever you do, postmaster must be run by the
- Postgres superuser (postgres?) and not by root.
- This is why all of the examples below start by
- switching user (su) to postgres. These commands
- also take into account the fact that environment
- variables like PATH and PGDATA may not be set
- properly. The examples are as follows. Use them
- with extreme caution.
- o If you are installing from a non-privileged
- account and have no root access, then start the
- postmaster and send it to the background:
- $ cd
- $ nohup postmaster > regress.log 2>&1 &
- o Edit file rc.local on NetBSD or file rc2.d on
- SPARC Solaris 2.5.1 to contain the following
- single line:
- su postgres -c "/usr/local/pgsql/bin/postmaster
- -S -D /usr/local/pgsql/data"
- o In FreeBSD 2.2-RELEASE edit
- /usr/local/etc/rc.d/pgsql.sh to contain the
- following lines and make it chmod 755 and chown
- root:bin.
- #!/bin/sh
- [ -x /usr/local/pgsql/bin/postmaster ] && {
- su -l pgsql -c 'exec
- /usr/local/pgsql/bin/postmaster
- -D/usr/local/pgsql/data
- -S -o -F > /usr/local/pgsql/errlog' &
- echo -n ' pgsql'
- }
- You may put the line breaks as shown above. The
- shell is smart enough to keep parsing beyond
- end-of-line if there is an expression unfinished.
- The exec saves one layer of shell under the
- postmaster process so the parent is init.
- o In RedHat Linux add a file
- /etc/rc.d/init.d/postgres.init which is based on
- the example in contrib/linux/. Then make a
- softlink to this file from
- /etc/rc.d/rc5.d/S98postgres.init.
- o In RedHat Linux edit file /etc/inittab to add the
- following as a single line:
- pg:2345:respawn:/bin/su - postgres -c
- "/usr/local/pgsql/bin/postmaster
- -D/usr/local/pgsql/data
- >> /usr/local/pgsql/server.log 2>&1
- </dev/null"
- (The author of this example says this example
- will revive the postmaster if it dies, but he
- doesn't know if there are other side effects.)
- 22. Run the regression tests. The file
- /usr/src/pgsql/src/test/regress/README has
- detailed instructions for running and interpreting
- the regression tests. A short version follows
- here:
- a. Type
- $ cd /usr/src/pgsql/src/test/regress
- $ gmake clean
- $ gmake all runtest
- You do not need to type gmake clean if this
- is the first time you are running the tests.
- You should get on the screen (and also
- written to file ./regress.out) a series of
- statements stating which tests passed and
- which tests failed. Please note that it can
- be normal for some tests to "fail" on some
- platforms. The script says a test has failed
- if there is any difference at all between the
- actual output of the test and the expected
- output. Thus, tests may "fail" due to minor
- differences in wording of error messages,
- small differences in floating-point roundoff,
- etc, between your system and the regression
- test reference platform. "Failures" of this
- type do not indicate a problem with Postgres.
- The file ./regression.diffs contains the
- textual differences between the actual test
- output on your machine and the "expected"
- output (which is simply what the reference
- system produced). You should carefully
- examine each difference listed to see whether
- it appears to be a significant issue.
- For example,
- o For a i686/Linux-ELF platform, no tests
- failed since this is the v6.5 regression
- testing reference platform.
- Even if a test result clearly indicates a
- real failure, it may be a localized problem
- that will not affect you. An example is that
- the int8 test will fail, producing obviously
- incorrect output, if your machine and C
- compiler do not provide a 64-bit integer data
- type (or if they do but configure didn't
- discover it). This is not something to worry
- about unless you need to store 64-bit
- integers.
- Conclusion? If you do see failures, try to
- understand the nature of the differences and
- then decide if those differences will affect
- your intended use of Postgres. The regression
- tests are a helpful tool, but they may
- require some study to be useful.
- After running the regression tests, type
- $ destroydb regression
- $ cd /usr/src/pgsql/src/test/regress
- $ gmake clean
- to recover the disk space used for the
- tests. (You may want to save the
- regression.diffs file in another place before
- doing this.)
- 23. If you haven't already done so, this would be
- a good time to modify your computer to do regular
- maintainence. The following should be done at
- regular intervals:
-
- Minimal Backup Procedure
- 1. Run the SQL command VACUUM. This will clean
- up your database.
- 2. Back up your system. (You should probably
- keep the last few backups on hand.) Preferably,
- no one else should be using the system at the
- time.
-
- Ideally, the above tasks should be done by a
- shell script that is run nightly or weekly by
- cron. Look at the man page for crontab for a
- starting point on how to do this. (If you do it,
- please e-mail us a copy of your shell script. We
- would like to set up our own systems to do this
- too.)
- 24. If you are upgrading an existing system then
- reinstall your old database. Type
- $ cd
- $ psql -e template1 < db.out
- If your pre-v6.2 database uses either path or
- polygon geometric data types, then you will need
- to upgrade any columns containing those types. To
- do so, type (from within psql)
- UPDATE FirstTable SET PathCol =
- UpgradePath(PathCol);
- UPDATE SecondTable SET PathCol =
- UpgradePath(PathCol);
- ...
- VACUUM;
- UpgradePath() checks to see that a path value is
- consistant with the old syntax, and will not
- update a column which fails that examination.
- UpgradePoly() cannot verify that a polygon is in
- fact from an old syntax, but RevertPoly() is
- provided to reverse the effects of a mis-applied
- upgrade.
- 25. If you are a new user, you may wish to play
- with Postgres as described below.
- 26. Clean up after yourself. Type
- $ rm -rf /usr/src/pgsql_6_5
- $ rm -rf /usr/local/pgsql_6_5
- # Also delete old database directory tree if it is
- not in
- # /usr/local/pgsql_6_5/data
- $ rm ~/postgresql-v6.5.1.tar.gz
- 27. You will probably want to print out the
- documentation. If you have a Postscript printer,
- or have your machine already set up to accept
- Postscript files using a print filter, then to
- print the User's Guide simply type
- $ cd /usr/local/pgsql/doc
- $ gunzip user.ps.tz | lpr
- Here is how you might do it if you have
- Ghostscript on your system and are writing to a
- laserjet printer.
- $ alias gshp='gs -sDEVICE=laserjet -r300
- -dNOPAUSE'
- $ export
- GS_LIB=/usr/share/ghostscript:/usr/share/ghostscr-
- ipt/fonts
- $ gunzip user.ps.gz
- $ gshp -sOUTPUTFILE=user.hp user.ps
- $ gzip user.ps
- $ lpr -l -s -r manpage.hp
- 28. The Postgres team wants to keep Postgres
- working on all of the supported platforms. We
- therefore ask you to let us know if you did or did
- not get Postgres to work on you system. Please
- send a mail message to pgsql-ports@postgresql.org
- (mailto:pgsql-ports@postgresql.org) telling us the
- following:
- o The version of Postgres (v6.5.1, 6.5, beta
- 990318, etc.).
- o Your operating system (i.e. RedHat v5.2 Linux
- v2.0.36).
- o Your hardware (SPARC, i486, etc.).
- o Did you compile, install and run the regression
- tests cleanly? If not, what source code did you
- change (i.e. patches you applied, changes you
- made, etc.), what tests failed, etc. It is normal
- to get many warning when you compile. You do not
- need to report these.
- 29. Now create, access and manipulate databases
- as desired. Write client programs to access the
- database server. In other words, enjoy!
+Postgres Installation
+
+For a fresh install or upgrading from previous releases of Postgres:
+
+ 1. Read any last minute information and platform specific porting notes.
+ There are some platform specific notes at the end of this file for
+ Ultrix4.x, Linux, BSD/OS and NeXT. There are other files in directory
+ /usr/src/pgsql/doc, including files FAQ-Irix and FAQ-Linux. Also look
+ in directory ftp://ftp.postgresql.org/pub. If there is a file called
+ INSTALL in this directory then this file will contain the latest
+ installation information.
+
+ Please note that a "tested" platform in the list given earlier simply
+ means that someone went to the effort at some point of making sure that
+ a Postgres distribution would compile and run on this platform without
+ modifying the code. Since the current developers will not have access
+ to all of these platforms, some of them may not compile cleanly and
+ pass the regression tests in the current release due to minor problems.
+ Any such known problems and their solutions will be posted in
+ ftp://ftp.postgresql.org/pub/INSTALL.
+
+ 2. Create the Postgres superuser account (postgres is commonly used) if it
+ does not already exist.
+
+ The owner of the Postgres files can be any unprivileged user account.
+ It must not be root, bin, or any other account with special access
+ rights, as that would create a security risk.
+
+ 3. Log in to the Postgres superuser account. Most of the remaining steps
+ in the installation will happen in this account.
+
+ 4. Ftp file ftp://ftp.postgresql.org/pub/postgresql-v6.5.3.tar.gz from the
+ Internet. Store it in your home directory.
+
+ 5. Some platforms use flex. If your system uses flex then make sure you
+ have a good version. To check, type
+
+ $ flex --version
+
+ If the flex command is not found then you probably do not need it. If
+ the version is 2.5.2 or 2.5.4 or greater then you are okay. If it is
+ 2.5.3 or before 2.5.2 then you will have to upgrade flex. You may get
+ it at ftp://prep.ai.mit.edu/pub/gnu/flex-2.5.4.tar.gz.
+
+ If you need flex and don't have it or have the wrong version, then you
+ will be told so when you attempt to compile the program. Feel free to
+ skip this step if you aren't sure you need it. If you do need it then
+ you will be told to install/upgrade flex when you try to compile
+ Postgres.
+
+ You may want to do the entire flex installation from the root account,
+ though that is not absolutely necessary. Assuming that you want the
+ installation to place files in the usual default areas, type the
+ following:
+
+ $ su -
+ $ cd /usr/local/src
+ ftp prep.ai.mit.edu
+ ftp> cd /pub/gnu/
+ ftp> binary
+ ftp> get flex-2.5.4.tar.gz
+ ftp> quit
+ $ gunzip -c flex-2.5.4.tar.gz | tar xvf -
+ $ cd flex-2.5.4
+ $ configure --prefix=/usr
+ $ gmake
+ $ gmake check
+ # You must be root when typing the next line:
+ $ gmake install
+ $ cd /usr/local/src
+ $ rm -rf flex-2.5.4
+
+ This will update files /usr/man/man1/flex.1, /usr/bin/flex,
+ /usr/lib/libfl.a, /usr/include/FlexLexer.h and will add a link
+ /usr/bin/flex++ which points to flex.
+
+ 6. If you are not upgrading an existing system then skip to . If you are
+ upgrading from 6.5, you do not need to dump/reload or initdb. Simply
+ compile the source code, stop the postmaster, do a "make install", and
+ restart the postmaster. If you are upgrading from 6.4.* or earlier,
+ back up your database. For alpha- and beta-level releases, the database
+ format is liable to change, often every few weeks, with no notice
+ besides a quick comment in the HACKERS mailing list. Full releases
+ always require a dump/reload from previous releases. It is therefore a
+ bad idea to skip this step.
+
+ Tip: Do not use the pg_dumpall script from v6.0 or everything
+ will be owned by the Postgres super user.
+
+ To dump your fairly recent post-v6.0 database installation, type
+
+ $ pg_dumpall > db.out
+
+ To use the latest pg_dumpall script on your existing older database
+ before upgrading Postgres, pull the most recent version of pg_dumpall
+ from the new distribution:
+
+ $ cd
+ $ gunzip -c postgresql-v6.5.3.tar.gz \
+ | tar xvf - src/bin/pg_dump/pg_dumpall
+ $ chmod a+x src/bin/pg_dump/pg_dumpall
+ $ src/bin/pg_dump/pg_dumpall > db.out
+ $ rm -rf src
+
+ If you wish to preserve object id's (oids), then use the -o option when
+ running pg_dumpall. However, unless you have a special reason for doing
+ this (such as using OIDs as keys in tables), don't do it.
+
+ If the pg_dumpall command seems to take a long time and you think it
+ might have died, then, from another terminal, type
+
+ $ ls -l db.out
+
+ several times to see if the size of the file is growing.
+
+ Please note that if you are upgrading from a version prior to
+ Postgres95 v1.09 then you must back up your database, install
+ Postgres95 v1.09, restore your database, then back it up again. You
+ should also read the release notes which should cover any
+ release-specific issues.
+
+ Caution
+ You must make sure that your database is not updated in the middle of your
+ backup. If necessary, bring down postmaster, edit the permissions in file
+ /usr/local/pgsql/data/pg_hba.conf to allow only you on, then bring
+ postmaster back up.
+ 7. If you are upgrading an existing system then kill the postmaster. Type
+
+ $ ps -ax | grep postmaster
+
+ This should list the process numbers for a number of processes. Type
+ the following line, with pid replaced by the process id for process
+ postmaster. (Do not use the id for process "grep postmaster".) Type
+
+ $ kill pid
+
+ to actually stop the process.
+
+ Tip: On systems which have Postgres started at boot time,
+ there is probably a startup file which will accomplish the
+ same thing. For example, on my Linux system I can type
+
+ $ /etc/rc.d/init.d/postgres.init stop
+
+ to halt Postgres.
+
+ 8. If you are upgrading an existing system then move the old directories
+ out of the way. If you are short of disk space then you may have to
+ back up and delete the directories instead. If you do this, save the
+ old database in the /usr/local/pgsql/data directory tree. At a minimum,
+ save file /usr/local/pgsql/data/pg_hba.conf.
+
+ Type the following:
+
+ $ su -
+ $ cd /usr/src
+ $ mv pgsql pgsql_6_0
+ $ cd /usr/local
+ $ mv pgsql pgsql_6_0
+ $ exit
+
+ If you are not using /usr/local/pgsql/data as your data directory
+ (check to see if environment variable PGDATA is set to something else)
+ then you will also want to move this directory in the same manner.
+
+ 9. Make new source and install directories. The actual paths can be
+ different for your installation but you must be consistent throughout
+ this procedure.
+
+ Note: There are two places in this installation procedure
+ where you will have an opportunity to specify installation
+ locations for programs, libraries, documentation, and other
+ files. Usually it is sufficient to specify these at the gmake
+ install stage of installation.
+
+ Type
+
+ $ su
+ $ cd /usr/src
+ $ mkdir pgsql
+ $ chown postgres:postgres pgsql
+ $ cd /usr/local
+ $ mkdir pgsql
+ $ chown postgres:postgres pgsql
+ $ exit
+
+ 10. Unzip and untar the new source file. Type
+
+ $ cd /usr/src/pgsql
+ $ gunzip -c ~/postgresql-v6.5.3.tar.gz | tar xvf -
+
+ 11. Configure the source code for your system. It is this step at which you
+ can specify your actual installation path for the build process (see
+ the --prefix option below). Type
+
+ $ cd /usr/src/pgsql/src
+ $ ./configure [ options ]
+
+ a. Among other chores, the configure script selects a system-specific
+ "template" file from the files provided in the template
+ subdirectory. If it cannot guess which one to use for your system,
+ it will say so and exit. In that case you'll need to figure out
+ which one to use and run configure again, this time giving the
+ --with-template=TEMPLATE option to make the right file be chosen.
+
+ Please Report Problems: If your system is not
+ automatically recognized by configure and you have to do
+ this, please send email to scrappy@hub.org with the
+ output of the program ./config.guess. Indicate what the
+ template file should be.
+
+ b. Choose configuration options. Check for details. However, for a
+ plain-vanilla first installation with no extra options like
+ multi-byte character support or locale collation support it may be
+ adequate to have chosen the installation areas and to run
+ configure without extra options specified. The configure script
+ accepts many additional options that you can use if you don't like
+ the default configuration. To see them all, type
+
+ ./configure --help
+
+ Some of the more commonly used ones are:
+
+ --prefix=BASEDIR Selects a different base directory for the
+ installation of the Postgres configuration.
+ The default is /usr/local/pgsql.
+ --with-template=TEMPLATE
+ Use template file TEMPLATE - the template
+ files are assumed to be in the directory
+ src/template, so look there for proper values.
+ --with-tcl Build interface libraries and programs requiring
+ Tcl/Tk, including libpgtcl, pgtclsh, and pgtksh.
+ --with-perl Build the Perl interface library.
+ --with-odbc Build the ODBC driver package.
+ --enable-hba Enables Host Based Authentication (DEFAULT)
+ --disable-hba Disables Host Based Authentication
+ --enable-locale Enables USE_LOCALE
+ --enable-cassert Enables ASSERT_CHECKING
+ --with-CC=compiler
+ Use a specific C compiler that the configure
+ script cannot find.
+ --with-CXX=compiler
+ --without-CXX
+ Use a specific C++ compiler that the configure
+ script cannot find, or exclude C++ compilation
+ altogether. (This only affects libpq++ at
+ present.)
+
+ c. Here is the configure script used on a Sparc Solaris 2.5 system
+ with /opt/postgres specified as the installation base directory:
+
+ $ ./configure --prefix=/opt/postgres \
+ --with-template=sparc_solaris-gcc --with-pgport=5432 \
+ --enable-hba --disable-locale
+
+ Tip: Of course, you may type these three lines all on
+ the same line.
+
+ 12. Install the man and HTML documentation. Type
+
+ $ cd /usr/src/pgsql/doc
+ $ gmake install
+
+ The documentation is also available in Postscript format. Look for
+ files ending with .ps.gz in the same directory.
+
+ 13. Compile the program. Type
+
+ $ cd /usr/src/pgsql/src
+ $ gmake all > make.log 2>&1 &
+ $ tail -f make.log
+
+ The last line displayed will hopefully be
+
+ All of PostgreSQL is successfully made. Ready to install.
+
+ Remember, "gmake" may be called "make" on your system. At this point,
+ or earlier if you wish, type control-C to get out of tail. (If you have
+ problems later on you may wish to examine file make.log for warning and
+ error messages.)
+
+ Note: You will probably find a number of warning messages in
+ make.log. Unless you have problems later on, these messages
+ may be safely ignored.
+
+ If the compiler fails with a message stating that the flex command
+ cannot be found then install flex as described earlier. Next, change
+ directory back to this directory, type
+
+ $ gmake clean
+
+ then recompile again.
+
+ Compiler options, such as optimization and debugging, may be specified
+ on the command line using the COPT variable. For example, typing
+
+ $ gmake COPT="-g" all > make.log 2>&1 &
+
+ would invoke your compiler's -g option in all steps of the build. See
+ src/Makefile.global.in for further details.
+
+ 14. Install the program. Type
+
+ $ cd /usr/src/pgsql/src
+ $ gmake install > make.install.log 2>&1 &
+ $ tail -f make.install.log
+
+ The last line displayed will be
+
+ gmake[1]: Leaving directory `/usr/src/pgsql/src/man'
+
+ At this point, or earlier if you wish, type control-C to get out of
+ tail. Remember, "gmake" may be called "make" on your system.
+
+ 15. If necessary, tell your system how to find the new shared libraries.
+ You can do one of the following, preferably the first:
+
+ a. As root, edit file /etc/ld.so.conf. Add a line
+
+ /usr/local/pgsql/lib
+
+ to the file. Then run command /sbin/ldconfig.
+
+ b. In a bash shell, type
+
+ export LD_LIBRARY_PATH=/usr/local/pgsql/lib
+
+ c. In a csh shell, type
+
+ setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
+
+ Please note that the above commands may vary wildly for different
+ operating systems. Check the platform specific notes, such as those for
+ Ultrix4.x or and for non-ELF Linux.
+
+ If, when you create the database, you get the message
+
+ pg_id: can't load library 'libpq.so'
+
+ then the above step was necessary. Simply do this step, then try to
+ create the database again.
+
+ 16. If you used the --with-perl option to configure, check the install log
+ to see whether the Perl module was actually installed. If you've
+ followed our advice to make the Postgres files be owned by an
+ unprivileged userid, then the Perl module won't have been installed,
+ for lack of write privileges on the Perl library directories. You can
+ complete its installation, either now or later, by becoming the user
+ that does own the Perl library (often root) (via su) and doing
+
+ $ cd /usr/src/pgsql/src/interfaces/perl5
+ $ gmake install
+
+
+ 17. If it has not already been done, then prepare account postgres for
+ using Postgres. Any account that will use Postgres must be similarly
+ prepared.
+
+ There are several ways to influence the runtime environment of the
+ Postgres server. Refer to the Administrator's Guide for more
+ information.
+
+ Note: The following instructions are for a bash/sh shell.
+ Adapt accordingly for other shells.
+
+ a. Add the following lines to your login environment: shell,
+ ~/.bash_profile:
+
+ PATH=$PATH:/usr/local/pgsql/bin
+ MANPATH=$MANPATH:/usr/local/pgsql/man
+ PGLIB=/usr/local/pgsql/lib
+ PGDATA=/usr/local/pgsql/data
+ export PATH MANPATH PGLIB PGDATA
+
+
+ b. Several regression tests could fail if the user's locale collation
+ scheme is different from that of the standard C locale.
+
+ If you configure and compile Postgres with --enable-locale then
+ you should set the locale environment to "C" (or unset all "LC_*"
+ variables) by putting these additional lines to your login
+ environment before starting postmaster:
+
+ LC_COLLATE=C
+ LC_CTYPE=C
+ export LC_COLLATE LC_CTYPE
+
+
+
+
+
+ c. Make sure that you have defined these variables before continuing
+ with the remaining steps. The easiest way to do this is to type:
+
+ $ source ~/.bash_profile
+
+
+ 18. Create the database installation from your Postgres superuser account
+ (typically account postgres). Do not do the following as root! This
+ would be a major security hole. Type
+
+ $ initdb
+
+ 19. Set up permissions to access the database system. Do this by editing
+ file /usr/local/pgsql/data/pg_hba.conf. The instructions are included
+ in the file. (If your database is not located in the default location,
+ i.e. if PGDATA is set to point elsewhere, then the location of this
+ file will change accordingly.) This file should be made read only again
+ once you are finished. If you are upgrading from v6.0 or later you can
+ copy file pg_hba.conf from your old database on top of the one in your
+ new database, rather than redoing the file from scratch.
+
+ 20. Briefly test that the backend will start and run by running it from the
+ command line.
+
+ a. Start the postmaster daemon running in the background by typing
+
+ $ cd
+ $ nohup postmaster -i > pgserver.log 2>&1 &
+
+ b. Create a database by typing
+
+ $ createdb
+
+ c. Connect to the new database:
+
+ $ psql
+
+ d. And run a sample query:
+
+ postgres=> SELECT datetime 'now';
+
+ e. Exit psql:
+
+ postgres=> \q
+
+ f. Remove the test database (unless you will want to use it later for
+ other tests):
+
+ $ destroydb
+
+ 21. Run postmaster in the background from your Postgres superuser account
+ (typically account postgres). Do not run postmaster from the root
+ account!
+
+ Usually, you will want to modify your computer so that it will
+ automatically start postmaster whenever it boots. It is not required;
+ the Postgres server can be run successfully from non-privileged
+ accounts without root intervention.
+
+ Here are some suggestions on how to do this, contributed by various
+ users.
+
+ Whatever you do, postmaster must be run by the Postgres superuser
+ (postgres?) and not by root. This is why all of the examples below
+ start by switching user (su) to postgres. These commands also take into
+ account the fact that environment variables like PATH and PGDATA may
+ not be set properly. The examples are as follows. Use them with extreme
+ caution.
+
+ o If you are installing from a non-privileged account and have no
+ root access, then start the postmaster and send it to the
+ background:
+
+ $ cd
+ $ nohup postmaster > regress.log 2>&1 &
+
+ o Edit file rc.local on NetBSD or file rc2.d on SPARC Solaris 2.5.1
+ to contain the following single line:
+
+ su postgres -c "/usr/local/pgsql/bin/postmaster -S -D /usr/local/pgsql/data"
+
+ o In FreeBSD 2.2-RELEASE edit /usr/local/etc/rc.d/pgsql.sh to
+ contain the following lines and make it chmod 755 and chown
+ root:bin.
+
+ #!/bin/sh
+ [ -x /usr/local/pgsql/bin/postmaster ] && {
+ su -l pgsql -c 'exec /usr/local/pgsql/bin/postmaster
+ -D/usr/local/pgsql/data
+ -S -o -F > /usr/local/pgsql/errlog' &
+ echo -n ' pgsql'
+ }
+
+ You may put the line breaks as shown above. The shell is smart
+ enough to keep parsing beyond end-of-line if there is an
+ expression unfinished. The exec saves one layer of shell under the
+ postmaster process so the parent is init.
+
+ o In RedHat Linux add a file /etc/rc.d/init.d/postgres.init which is
+ based on the example in contrib/linux/. Then make a softlink to
+ this file from /etc/rc.d/rc5.d/S98postgres.init.
+
+ o In RedHat Linux edit file /etc/inittab to add the following as a
+ single line:
+
+ pg:2345:respawn:/bin/su - postgres -c
+ "/usr/local/pgsql/bin/postmaster -D/usr/local/pgsql/data
+ /usr/local/pgsql/server.log 2&1 /dev/null"
+
+ (The author of this example says this example will revive the
+ postmaster if it dies, but he doesn't know if there are other side
+ effects.)
+
+ 22. Run the regression tests. The file
+ /usr/src/pgsql/src/test/regress/README has detailed instructions for
+ running and interpreting the regression tests. A short version follows
+ here:
+
+ a. Type
+
+ $ cd /usr/src/pgsql/src/test/regress
+ $ gmake clean
+ $ gmake all runtest
+
+ You do not need to type gmake clean if this is the first time you
+ are running the tests.
+
+ You should get on the screen (and also written to file
+ ./regress.out) a series of statements stating which tests passed
+ and which tests failed. Please note that it can be normal for some
+ tests to "fail" on some platforms. The script says a test has
+ failed if there is any difference at all between the actual output
+ of the test and the expected output. Thus, tests may "fail" due to
+ minor differences in wording of error messages, small differences
+ in floating-point roundoff, etc, between your system and the
+ regression test reference platform. "Failures" of this type do not
+ indicate a problem with Postgres. The file ./regression.diffs
+ contains the textual differences between the actual test output on
+ your machine and the "expected" output (which is simply what the
+ reference system produced). You should carefully examine each
+ difference listed to see whether it appears to be a significant
+ issue.
+
+ For example,
+
+ + For a i686/Linux-ELF platform, no tests failed since this is
+ the v6.5.3 regression testing reference platform.
+
+ Even if a test result clearly indicates a real failure, it may be
+ a localized problem that will not affect you. An example is that
+ the int8 test will fail, producing obviously incorrect output, if
+ your machine and C compiler do not provide a 64-bit integer data
+ type (or if they do but configure didn't discover it). This is not
+ something to worry about unless you need to store 64-bit integers.
+
+ Conclusion? If you do see failures, try to understand the nature
+ of the differences and then decide if those differences will
+ affect your intended use of Postgres. The regression tests are a
+ helpful tool, but they may require some study to be useful.
+
+ After running the regression tests, type
+
+ $ destroydb regression
+ $ cd /usr/src/pgsql/src/test/regress
+ $ gmake clean
+
+ to recover the disk space used for the tests. (You may want to
+ save the regression.diffs file in another place before doing
+ this.)
+
+ 23. If you haven't already done so, this would be a good time to modify
+ your computer to do regular maintainence. The following should be done
+ at regular intervals:
+
+ Minimal Backup Procedure
+
+ 1. Run the SQL command VACUUM. This will clean up your database.
+
+ 2. Back up your system. (You should probably keep the last few
+ backups on hand.) Preferably, no one else should be using the
+ system at the time.
+
+ Ideally, the above tasks should be done by a shell script that is run
+ nightly or weekly by cron. Look at the man page for crontab for a
+ starting point on how to do this. (If you do it, please e-mail us a
+ copy of your shell script. We would like to set up our own systems to
+ do this too.)
+
+ 24. If you are upgrading an existing system then reinstall your old
+ database. Type
+
+ $ cd
+ $ psql -e template1 < db.out
+
+ If your pre-v6.2 database uses either path or polygon geometric data
+ types, then you will need to upgrade any columns containing those
+ types. To do so, type (from within psql)
+
+ UPDATE FirstTable SET PathCol = UpgradePath(PathCol);
+ UPDATE SecondTable SET PathCol = UpgradePath(PathCol);
+ ...
+ VACUUM;
+
+ UpgradePath() checks to see that a path value is consistant with the
+ old syntax, and will not update a column which fails that examination.
+ UpgradePoly() cannot verify that a polygon is in fact from an old
+ syntax, but RevertPoly() is provided to reverse the effects of a
+ mis-applied upgrade.
+
+ 25. If you are a new user, you may wish to play with Postgres as described
+ below.
+
+ 26. Clean up after yourself. Type
+
+ $ rm -rf /usr/src/pgsql_6_5
+ $ rm -rf /usr/local/pgsql_6_5
+ # Also delete old database directory tree if it is not in
+ # /usr/local/pgsql_6_5/data
+ $ rm ~/postgresql-v6.5.3.tar.gz
+
+ 27. You will probably want to print out the documentation. If you have a
+ Postscript printer, or have your machine already set up to accept
+ Postscript files using a print filter, then to print the User's Guide
+ simply type
+
+ $ cd /usr/local/pgsql/doc
+ $ gunzip user.ps.tz | lpr
+
+ Here is how you might do it if you have Ghostscript on your system and
+ are writing to a laserjet printer.
+
+ $ alias gshp='gs -sDEVICE=laserjet -r300 -dNOPAUSE'
+ $ export GS_LIB=/usr/share/ghostscript:/usr/share/ghostscript/fonts
+ $ gunzip user.ps.gz
+ $ gshp -sOUTPUTFILE=user.hp user.ps
+ $ gzip user.ps
+ $ lpr -l -s -r manpage.hp
+
+ 28. The Postgres team wants to keep Postgres working on all of the
+ supported platforms. We therefore ask you to let us know if you did or
+ did not get Postgres to work on you system. Please send a mail message
+ to pgsql-ports@postgresql.org telling us the following:
+
+ o The version of Postgres (v6.5.3, 6.5, beta 990318, etc.).
+
+ o Your operating system (i.e. RedHat v5.1 Linux v2.0.34).
+
+ o Your hardware (SPARC, i486, etc.).
+
+ o Did you compile, install and run the regression tests cleanly? If
+ not, what source code did you change (i.e. patches you applied,
+ changes you made, etc.), what tests failed, etc. It is normal to
+ get many warning when you compile. You do not need to report
+ these.
+
+ 29. Now create, access and manipulate databases as desired. Write client
+ programs to access the database server. In other words, enjoy!
+
+ ------------------------------------------------------------------------
Playing with Postgres
- After Postgres is installed, a database system is
- created, a postmaster daemon is running, and the
- regression tests have passed, you'll want to see
- Postgres do something. That's easy. Invoke the
- interactive interface to Postgres, psql:
+After Postgres is installed, a database system is created, a postmaster
+daemon is running, and the regression tests have passed, you'll want to see
+Postgres do something. That's easy. Invoke the interactive interface to
+Postgres, psql:
- % psql template1
+% psql template1
- (psql has to open a particular database, but at this
- point the only one that exists is the template1
- database, which always exists. We will connect to it
- only long enough to create another one and switch to
- it.)
- The response from psql is:
+(psql has to open a particular database, but at this point the only one that
+exists is the template1 database, which always exists. We will connect to it
+only long enough to create another one and switch to it.)
- Welcome to the POSTGRESQL interactive sql monitor:
- Please read the file COPYRIGHT for copyright terms
- of POSTGRESQL
+The response from psql is:
- type \? for help on slash commands
- type \q to quit
- type \g or terminate with semicolon to execute
- query
- You are currently connected to the database:
- template1
+Welcome to the POSTGRESQL interactive sql monitor:
+ Please read the file COPYRIGHT for copyright terms of POSTGRESQL
- template1=>
+ type \? for help on slash commands
+ type \q to quit
+ type \g or terminate with semicolon to execute query
+ You are currently connected to the database: template1
- Create the database foo:
+template1=>
- template1=> create database foo;
- CREATEDB
+Create the database foo:
- (Get in the habit of including those SQL semicolons.
- Psql won't execute anything until it sees the
- semicolon or a "\g" and the semicolon is required to
- delimit multiple statements.)
- Now connect to the new database:
+template1=> create database foo;
+CREATEDB
- template1=> \c foo
- connecting to new database: foo
+(Get in the habit of including those SQL semicolons. Psql won't execute
+anything until it sees the semicolon or a "\g" and the semicolon is required
+to delimit multiple statements.)
- ("slash" commands aren't SQL, so no semicolon. Use \?
- to see all the slash commands.)
- And create a table:
+Now connect to the new database:
- foo=> create table bar (i int4, c char(16));
- CREATE
+template1=> \c foo
+connecting to new database: foo
- Then inspect the new table:
+("slash" commands aren't SQL, so no semicolon. Use \? to see all the slash
+commands.)
- foo=> \d bar
+And create a table:
- Table = bar
- +----------------------------------+-----------------
- ------------------+-------+
- | Field |
- Type | Length|
- +----------------------------------+-----------------
- ------------------+-------+
- | i | int4
- | 4 |
- | c | (bp)char
- | 16 |
- +----------------------------------+-----------------
- ------------------+-------+
+foo=> create table bar (i int4, c char(16));
+CREATE
+
+Then inspect the new table:
+
+foo=> \d bar
+
+Table = bar
++----------------------------------+----------------------------------+-------+
+| Field | Type | Length|
++----------------------------------+----------------------------------+-------+
+| i | int4 | 4 |
+| c | (bp)char | 16 |
++----------------------------------+----------------------------------+-------+
+
+And so on. You get the idea.
+
+ ------------------------------------------------------------------------
- And so on. You get the idea.
The Next Step
- Questions? Bugs? Feedback? First, read the files in
- directory /usr/src/pgsql/doc/. The FAQ in this
- directory may be particularly useful.
- If Postgres failed to compile on your computer then
- fill out the form in file
- /usr/src/pgsql/doc/bug.template and mail it to the
- location indicated at the top of the form.
- Check on the web site at http://www.postgresql.org
- For more information on the various support mailing
- lists.
+Questions? Bugs? Feedback? First, read the files in directory
+/usr/src/pgsql/doc/. The FAQ in this directory may be particularly useful.
-Porting Notes
+If Postgres failed to compile on your computer then fill out the form in
+file /usr/src/pgsql/doc/bug.template and mail it to the location indicated
+at the top of the form.
+
+Check on the web site at http://www.postgresql.org For more information on
+the various support mailing lists.
- Check for any platform-specific FAQs in the doc/
- directory of the source distribution.
-
-Chapter 4. Configuration Options
-
-Parameters for Configuration (configure)
-
- The full set of parameters available in configure
- can be obtained by typing
-
- $ ./configure --help
-
-
-
- The following parameters may be of interest to
- installers:
-
- Directory and file names:
- --prefix=PREFIX install
- architecture-independent files in PREFIX
- [/usr/local/pgsql]
- --bindir=DIR user executables in DIR
- [EPREFIX/bin]
- --libdir=DIR object code libraries in
- DIR [EPREFIX/lib]
- --includedir=DIR C header files in DIR
- [PREFIX/include]
- --mandir=DIR man documentation in DIR
- [PREFIX/man]
- Features and packages:
- --disable-FEATURE do not include FEATURE
- (same as --enable-FEATURE=no)
- --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
- --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
- --without-PACKAGE do not use PACKAGE (same as
- --with-PACKAGE=no)
- --enable and --with options recognized:
- --with-template=template
- use operating system
- template file
- see template directory
- --with-includes=incdir site header files for
- tk/tcl, etc in DIR
- --with-libs=incdir also search for libraries
- in DIR
- --with-libraries=libdir also search for libraries
- in DIR
- --enable-locale enable locale support
- --enable-recode enable cyrillic recode
- support
- --with-mb=encoding enable multi-byte support
- --with-pgport=portnum change default startup port
- --with-maxbackends=n set default maximum number of
- server processes
- --with-tcl build Tcl interfaces and
- pgtclsh
- --with-tclconfig=tcldir tclConfig.sh and
- tkConfig.sh are in DIR
- --with-perl build Perl interface
- --with-odbc build ODBC driver package
- --with-odbcinst=odbcdir change default directory
- for odbcinst.ini
- --enable-cassert enable assertion checks
- (debugging)
- --with-CC=compiler use specific C compiler
- --with-CXX=compiler use specific C++ compiler
- --without-CXX prevent building C++ code
-
-
-
- Some systems may have trouble building a specific
- feature of Postgres. For example, systems with a
- damaged C++ compiler may need to specify
- --without-CXX to instruct the build procedure to skip
- construction of libpq++.
-
-Parameters for Building (make)
-
- Many installation-related parameters can be set in
- the building stage of Postgres installation.
- In most cases, these parameters should be placed in
- a file, Makefile.custom, intended just for that
- purpose. The default distribution does not contain
- this optional file, so you will create it using a
- text editor of your choice. When upgrading
- installations, you can simply copy your old
- Makefile.custom to the new installation before doing
- the build.
-
- make [ variable=value [,...] ]
-
-
-
- A few of the many variables which can be specified
- are:
-
- POSTGRESDIR
- Top of the installation tree.
-
- BINDIR
- Location of applications and utilities.
-
- LIBDIR
- Location of object libraries, including shared
- libraries.
-
- HEADERDIR
- Location of include files.
-
- ODBCINST
- Location of installation-wide psqlODBC (ODBC)
- configuration file.
-
- There are other optional parameters which are not as
- commonly used. Many of those listed below are
- appropriate when doing Postgres server code
- development.
-
- CFLAGS
- Set flags for the C compiler. Should be assigned
- with "+=" to retain relevant default parameters.
-
- YFLAGS
- Set flags for the yacc/bison parser. -v might be
- used to help diagnose problems building a new
- parser. Should be assigned with "+=" to retain
- relevant default parameters.
-
- USE_TCL
- Enable Tcl interface building.
-
- HSTYLE
- DocBook HTML style sheets for building the
- documentation from scratch. Not used unless you
- are developing new documentation from the
- DocBook-compatible SGML source documents in
- doc/src/sgml/.
-
- PSTYLE
- DocBook style sheets for building printed
- documentation from scratch. Not used unless you
- are developing new documentation from the
- DocBook-compatible SGML source documents in
- doc/src/sgml/.
-
- Here is an example Makefile.custom for a PentiumPro
- Linux system:
-
- # Makefile.custom
- # Thomas Lockhart 1998-03-01
-
- POSTGRESDIR= /opt/postgres/current
- CFLAGS+= -m486 # -g -O0
- USE_TCL= true
- TCL_LIB= -ltcl
- X_LIBS= -L/usr/X11/lib
- TK_LIB= -ltk
-
- # documentation
-
- HSTYLE= /home/tgl/SGML/db118.d/docbook/html
- PSTYLE= /home/tgl/SGML/db118.d/docbook/print
-
-
-
-
-Locale Support
-
-
-
- Note: Written by Oleg Bartunov. See Oleg's web
- page (http://www.sai.msu.su/~megera/postgres/) for
- additional information on locale and Russian
- language support.
-
- While doing a project for a company in Moscow,
- Russia, I encountered the problem that postgresql had
- no support of national alphabets. After looking for
- possible workarounds I decided to develop support of
- locale myself. I'm not a C-programer but already had
- some experience with locale programming when I work
- with perl (debugging) and glimpse. After several days
- of digging through the Postgres source tree I made
- very minor corections to
- src/backend/utils/adt/varlena.c and
- src/backend/main/main.c and got what I needed! I did
- support only for LC_CTYPE and LC_COLLATE, but later
- LC_MONETARY was added by others. I got many messages
- from people about this patch so I decided to send it
- to developers and (to my surprise) it was
- incorporated into the Postgres distribution.
- People often complain that locale doesn't work for
- them. There are several common mistakes:
- o Didn't properly configure postgresql before
- compilation. You must run configure with
- --enable-locale option to enable locale support.
- Didn't setup environment correctly when starting
- postmaster. You must define environment variables
- LC_CTYPE and LC_COLLATE before running postmaster
- because backend gets information about locale from
- environment. I use following shell script
- (runpostgres):
- #!/bin/sh
-
- export LC_CTYPE=koi8-r
- export LC_COLLATE=koi8-r
- postmaster -B 1024 -S
- -D/usr/local/pgsql/data/ -o '-Fe'
-
- and run it from rc.local as
- /bin/su - postgres -c
- "/home/postgres/runpostgres"
-
-
- o Broken locale support in OS (for example, locale
- support in libc under Linux several times has
- changed and this caused a lot of problems). Latest
- perl has also support of locale and if locale is
- broken perl -v will complain something like:
- 8:17[mira]:~/WWW/postgres>setenv LC_CTYPE
- not_exist
- 8:18[mira]:~/WWW/postgres>perl -v
- perl: warning: Setting locale failed.
- perl: warning: Please check that your locale
- settings:
- LC_ALL = (unset),
- LC_CTYPE = "not_exist",
- LANG = (unset)
- are supported and installed on your system.
- perl: warning: Falling back to the standard
- locale ("C").
-
-
- o Wrong location of locale files! Possible locations
- include: /usr/lib/locale (Linux, Solaris),
- /usr/share/locale (Linux), /usr/lib/nls/loc (DUX
- 4.0). Check man locale to find the correct
- location. Under Linux I did a symbolic link between
- /usr/lib/locale and /usr/share/locale to be sure
- that the next libc will not break my locale.
-
-
-What are the Benefits?
-
- You can use ~* and order by operators for strings
- contain characters from national alphabets.
- Non-english users definitely need that. If you won't
- use locale stuff just undefine the USE_LOCALE
- variable.
-
-What are the Drawbacks?
-
- There is one evident drawback of using locale - its
- speed! So, use locale only if you really need it.
-
-Kerberos Authentication
-
- Kerberos is an industry-standard secure
- authentication system suitable for distributed
- computing over a public network.
-
-Availability
-
- The Kerberos authentication system is not
- distributed with Postgres. Versions of Kerberos are
- typically available as optional software from
- operating system vendors. In addition, a source code
- distribution may be obtained through MIT Project
- Athena (ftp://athena-dist.mit.edu).
-
- Note: You may wish to obtain the MIT version even
- if your vendor provides a version, since some
- vendor ports have been deliberately crippled or
- rendered non-interoperable with the MIT version.
-
- Users located outside the United States of America
- and Canada are warned that distribution of the actual
- encryption code in Kerberos is restricted by U. S.
- Government export regulations.
- Inquiries regarding your Kerberos should be directed
- to your vendor or MIT Project Athena
- (info-kerberos@athena.mit.edu). Note that FAQLs
- (Frequently-Asked Questions Lists) are periodically
- posted to the Kerberos mailing list
- (mailto:kerberos@ATHENA.MIT.EDU) (send mail to
- subscribe (mailto:kerberos-request@ATHENA.MIT.EDU)),
- and USENET news group (news:comp.protocols.kerberos).
-
-Installation
-
- Installation of Kerberos itself is covered in detail
- in the Kerberos Installation Notes . Make sure that
- the server key file (the srvtab or keytab) is somehow
- readable by the Postgres account.
- Postgres and its clients can be compiled to use
- either Version 4 or Version 5 of the MIT Kerberos
- protocols by setting the KRBVERS variable in the file
- src/Makefile.global to the appropriate value. You can
- also change the location where Postgres expects to
- find the associated libraries, header files and its
- own server key file.
- After compilation is complete, Postgres must be
- registered as a Kerberos service. See the Kerberos
- Operations Notes and related manual pages for more
- details on registering services.
-
-Operation
-
- After initial installation, Postgres should operate
- in all ways as a normal Kerberos service. For details
- on the use of authentication, see the PostgreSQL
- User's Guide reference sections for postmaster and
- psql.
- In the Kerberos Version 5 hooks, the following
- assumptions are made about user and service naming:
- o User principal names (anames) are assumed to
- contain the actual Unix/Postgres user name in the
- first component.
- o The Postgres service is assumed to be have two
- components, the service name and a hostname,
- canonicalized as in Version 4 (i.e., with all
- domain suffixes removed).
-
-
-
- Table 4-1. Kerberos Parameter Examples
- Parameter Example
- user frew@S2K.ORG
- user aoki/HOST=miyu.S2K.Berkeley.EDU@S2K.ORG
- host postgres_dbms/ucbvax@S2K.ORG
-
-
-
- Support for Version 4 will disappear sometime after
- the production release of Version 5 by MIT.
-
-Chapter 5. Release Notes
-
-Release 6.5
-
- This release marks a major step in the development
- team's mastery of the source code we inherited from
- Berkeley. You will see we are now easily adding major
- features, thanks to the increasing size and
- experience of our world-wide development team.
- Here is a brief summary of some of the more
- noticable changes:
-
- Multi-version concurrency control(MVCC)
- This removes our old table-level locking, and
- replaces it with a locking system that is superior
- to most commercial database systems. In a
- traditional system, each row that is modified is
- locked until committed, preventing reads by other
- users. MVCC uses the natural multi-version nature
- of PostgreSQL to allow readers to continue reading
- consistent data during writer activity. Writers
- continue to use the compact pg_log transaction
- system. This is all performed without having to
- allocate a lock for every row like traditional
- database systems. So, basically, we no longer are
- restricted by simple table-level locking; we have
- something better than row-level locking.
-
- Numeric data type
- We now have a true numeric data type, with
- user-specified precision.
-
- Temporary tables
- Temporary tables are guaranteed to have unique
- names within a database session, and are destroyed
- on session exit.
-
- New SQL features
- We now have CASE, INTERSECT, and EXCEPT statement
- support. We have new LIMIT/OFFSET, SET TRANSACTION
- ISOLATION LEVEL, SELECT ... FOR UPDATE, and an
- improved LOCK command.
-
- Speedups
- We continue to speed up PostgreSQL, thanks to the
- variety of talents within our team. We have sped
- up memory allocation, optimization, table joins,
- and row transfer routines.
-
- Ports
- We continue to expand our port list, this time
- including WinNT/ix86 and NetBSD/arm32.
-
- Interfaces
- Most interfaces have new versions, and existing
- functionality has been improved.
-
-
-Migration to v6.5
-
- A dump/restore using pg_dump or pg_dumpall is
- required for those wishing to migrate data from any
- previous release of Postgres.
- The new Multi-Version Concurrency Control (MVCC)
- features can give somewhat different behaviors in
- multi-user environments. Read and understand the
- following section to ensure that your existing
- applications will give you the behavior you need.
-
- Multi-Version Concurrency Control
- Because readers in 6.5 don't lock data, regardless
- of transaction isolation level, data read by one
- transaction can be overwritten by another. In the
- other words, if a row is returned by SELECT it
- doesn't mean that this row really exists at the time
- it is returned (i.e. sometime after the statement or
- transaction began) nor that the row is protected from
- deletion or updation by concurrent transactions
- before the current transaction does a commit or
- rollback.
- To ensure the actual existance of a row and protect
- it against concurrent updates one must use SELECT FOR
- UPDATE or an appropriate LOCK TABLE statement. This
- should be taken into account when porting
- applications from previous releases of Postgres and
- other environments.
- Keep above in mind if you are using contrib/refint.*
- triggers for referential integrity. Additional
- technics are required now. One way is to use LOCK
- parent_table IN SHARE ROW EXCLUSIVE MODE command if a
- transaction is going to update/delete a primary key
- and use LOCK parent_table IN SHARE MODE command if a
- transaction is going to update/insert a foreign key.
-
- Note: Note that if you run a transaction in
- SERIALIZABLE mode then you must execute LOCK
- commands above before execution of any DML
- statement
- (SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO) in the
- transaction.
-
-
- These inconveniences will disappear in the future
- when the ability to read dirty (uncommitted) data
- (regardless of isolation level) and true referential
- integrity will be implemented.
-
-Detailed Change List
-
-
-
- Bug Fixes
- ---------
- Fix text<->float8 and text<->float4 conversion
- functions(Thomas)
- Fix for creating tables with mixed-case
- constraints(Billy)
- Change exp()/pow() behavior to generate error on
- underflow/overflow(Jan)
- Fix bug in pg_dump -z
- Memory overrun cleanups(Tatsuo)
- Fix for lo_import crash(Tatsuo)
- Adjust handling of data type names to suppress double
- quotes(Thomas)
- Use type coersion for matching columns and
- DEFAULT(Thomas)
- Fix deadlock so it only checks once after one second
- of sleep(Bruce)
- Fixes for aggregates and PL/pgsql(Hiroshi)
- Fix for subquery crash(Vadim)
- Fix for libpq function PQfnumber and case-insensitive
- names(Bahman Rafatjoo)
- Fix for large object write-in-middle, no extra block,
- memory consumption(Tatsuo)
- Fix for pg_dump -d or -D and quote special
- characters in INSERT
- Repair serious problems with dynahash(Tom)
- Fix INET/CIDR portability problems
- Fix problem with selectivity error in ALTER TABLE ADD
- COLUMN(Bruce)
- Fix executor so mergejoin of different column types
- works(Tom)
- Fix for Alpha OR selectivity bug
- Fix OR index selectivity problem(Bruce)
- Fix so \d shows proper length for
- char()/varchar()(Ryan)
- Fix tutorial code(Clark)
- Improve destroyuser checking(Oliver)
- Fix for Kerberos(Rodney McDuff)
- Fix for dropping database while dirty buffers(Bruce)
- Fix so sequence nextval() can be
- case-sensitive(Bruce)
- Fix !!= operator
- Drop buffers before destroying database files(Bruce)
- Fix case where executor evaluates functions
- twice(Tatsuo)
- Allow sequence nextval actions to be
- case-sensitive(Bruce)
- Fix optimizer indexing not working for negative
- numbers(Bruce)
- Fix for memory leak in executor with fjIsNull
- Fix for aggregate memory leaks(Erik Riedel)
- Allow username containing a dash GRANT permissions
- Cleanup of NULL in inet types
- Clean up system table bugs(Tom)
- Fix problems of PAGER and \? command(Masaaki Sakaida)
- Reduce default multi-segment file size limit to
- 1GB(Peter)
- Fix for dumping of CREATE OPERATOR(Tom)
- Fix for backward scanning of cursors(Hiroshi Inoue)
- Fix for COPY FROM STDIN when using \i(Tom)
- Fix for subselect is compared inside an
- expression(Jan)
- Fix handling of error reporting while returning
- rows(Tom)
- Fix problems with reference to array types(Tom,Jan)
- Prevent UPDATE SET oid(Jan)
- Fix pg_dump so -t option can handle case-sensitive
- tablenames
- Fixes for GROUP BY in special cases(Tom, Jan)
- Fix for memory leak in failed queries(Tom)
- DEFAULT now supports mixed-case identifiers(Tom)
- Fix for multi-segment uses of DROP/RENAME table,
- indexes(Ole Gjerde)
-
- Enhancements
- ------------
- Add "vacuumdb" utility
- Speed up libpq by allocating memory better(Tom)
- EXPLAIN all indices used(Tom)
- Implement CASE, COALESCE, NULLIF expression(Thomas)
- New pg_dump table output format(Constantin)
- Add string min()/max() functions(Thomas)
- Extend new type coersion techniques to
- aggregates(Thomas)
- New moddatetime contrib(Terry)
- Update to pgaccess 0.96(Constantin)
- Add routines for single-byte "char" type(Thomas)
- Improved substr() function(Thomas)
- Improved multi-byte handling(Tatsuo)
- Multi-version concurrency control/MVCC(Vadim)
- New Serialized mode(Vadim)
- Fix for tables over 2gigs(Peter)
- New SET TRANSACTION ISOLATION LEVEL(Vadim)
- New LOCK TABLE IN ... MODE(Vadim)
- Update ODBC driver(Byron)
- New NUMERIC data type(Jan)
- New SELECT FOR UPDATE(Vadim)
- Handle "NaN" and "Infinity" for input values(Jan)
- Improved date/year handling(Thomas)
- Improved handling of backend connections(Magnus)
- New options ELOG_TIMESTAMPS and USE_SYSLOG options
- for log files(Massimo)
- New TCL_ARRAYS option(Massimo)
- New INTERSECT and EXCEPT(Stefan)
- New pg_index.indisprimary for primary key
- tracking(D'Arcy)
- New pg_dump option to allow dropping of tables before
- creation(Brook)
- Speedup of row output routines(Tom)
- New READ COMMITTED isolation level(Vadim)
- New TEMP tables/indexes(Bruce)
- Prevent sorting if result is already sorted(Jan)
- New memory allocation optimization(Jan)
- Allow psql to do \p\g(Bruce)
- Allow multiple rule actions(Jan)
- Added LIMIT/OFFSET functionality(Jan)
- Improve optimizer when joining a large number of
- tables(Bruce)
- New intro to SQL from S. Simkovics' Master's Thesis
- (Stefan, Thomas)
- New intro to backend processing from S. Simkovics'
- Master's Thesis (Stefan)
- Improved int8 support(Ryan Bradetich, Thomas, Tom)
- New routines to convert between int8 and text/varchar
- types(Thomas)
- New bushy plans, where meta-tables are joined(Bruce)
- Enable right-hand queries by default(Bruce)
- Allow reliable maximum number of backends to be set
- at configure time
- (--with-maxbackends and postmaster switch (-N
- backends))(Tom)
- GEQO default now 10 tables because of optimizer
- speedups(Tom)
- Allow NULL=Var for MS-SQL portability(Michael, Bruce)
- Modify contrib check_primary_key() so either
- "automatic" or "dependent"(Anand)
- Allow psql \d on a view show query(Ryan)
- Speedup for LIKE(Bruce)
- Ecpg fixes/features, see
- src/interfaces/ecpg/ChangeLog file(Michael)
- JDBC fixes/features, see
- src/interfaces/jdbc/CHANGELOG(Peter)
- Make % operator have precedence like /(Bruce)
- Add new postgres -O option to allow system table
- structure changes(Bruce)
- Update contrib/pginterface/findoidjoins script(Tom)
- Major speedup in vacuum of deleted rows with
- indexes(Vadim)
- Allow non-SQL functions to run different versions
- based on arguments(Tom)
- Add -E option that shows actual queries sent by \dt
- and friends(Masaaki Sakaida)
- Add version number in startup banners for
- psql(Masaaki Sakaida)
- New contrib/vacuumlo removes large objects not
- referenced(Peter)
- New initialization for table sizes so non-vacuumed
- tables perform better(Tom)
- Improve error messages when a connection is
- rejected(Tom)
- Support for arrays of char() and varchar()
- fields(Massimo)
- Overhaul of hash code to increase reliability and
- performance(Tom)
- Update to PyGreSQL 2.4(D'Arcy)
- Changed debug options so -d4 and -d5 produce
- different node displays(Jan)
- New pg_options: pretty_plan, pretty_parse,
- pretty_rewritten(Jan)
- Better optimization statistics for system table
- access(Tom)
- Better handling of non-default block sizes(Massimo)
- Improve GEQO optimizer memory consumption(Tom)
- UNION now suppports ORDER BY of columns not in target
- list(Jan)
- Major libpq++ improvements(Vince Vielhaber)
-
- Source Tree Changes
- -------------------
- Improve port matching(Tom)
- Portability fixes for SunOS
- Add NT/Win32 backend port and enable dynamic
- loading(Magnus and Daniel Horak)
- New port to Cobalt Qube(Mips) running Linux(Tatsuo)
- Port to NetBSD/m68k(Mr. Mutsuki Nakajima)
- Port to NetBSD/sun3(Mr. Mutsuki Nakajima)
- Port to NetBSD/macppc(Toshimi Aoki)
- Fix for tcl/tk configuration(Vince)
- Removed CURRENT keyword for rule queries(Jan)
- NT dynamic loading now works(Daniel Horak)
- Add ARM32 support(Andrew McMurry)
- Better support for HPUX 11 and Unixware
- Improve file handling to be more uniform, prevent
- file descriptor leak(Tom)
- New install commands for plpgsql(Jan)
-
+ ------------------------------------------------------------------------
+Porting Notes
+
+Check for any platform-specific FAQs in the doc/ directory of the source
+distribution.
projects / thirdparty / postgresql.git / commitdiff
