- FREQUENTLY ASKED QUESTIONS (FAQ) FOR POSTGRESQL
+ Frequently Asked Questions (FAQ) for PostgreSQL
-
-
- Last updated: Thu Mar 6 17:44:07 EST 1997
- Version: 6.0
+ Last updated: Tue May 13 23:15:59 EDT 1997
+ Version: 6.1
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
-
The most recent version of this document can be viewed at the
postgreSQL Web site, http://postgreSQL.org.
Changes in this version (* = modified, + = new):
* 3.42) What is Genetic Query Optimization?
+ * 3.43) I am running Solaris and my dates display wrong. Why?
-
_________________________________________________________________
-
-
-
+
Questions answered:
- 1) General questions
+ 1) General questions
1.1) What is PostgreSQL?
1.2) What does PostgreSQL run on?
/usr/local/pgsql?
2.5) When I run postmaster, I get a Bad System Call core dumped
message.
- 2.6) When I try to start the postmaster, I get IpcMemoryCreate errors.
- 2.7) I have changed a source file, but a recompile does not see the
- change.
+ 2.6) I get the error message "obj/fmgr.h: No such file or directory"
+ 2.7) When I try to start the postmaster, I get IpcMemoryCreate errors.
2.8) I have changed a source file, but a recompile does not see the
change?
3.40) What is an oid? What is a tid?
3.41) What is the meaning of some of the terms used in Postgres?
3.42) What is Genetic Query Optimization?
+ 3.42) I am running Solaris and my dates display wrong. Why?
4) Questions about extending PostgreSQL
5.1) How do I make a bug report?
_________________________________________________________________
-
+
Section 1: General Questions
1.1) What is PostgreSQL?
-
-
PostgreSQL is an enhancement of the POSTGRES database management
system, a next-generation DBMS research prototype. While PostgreSQL
retains the powerful data model and rich data types of POSTGRES, it
PostgreSQL development is being performed by a team of Internet
developers who all subscribe to the PostgreSQL development mailing
list. The current coordinator is Marc G. Fournier
- (scrappy@postgreSQL.org). (See below on how to join). This team is
- now responsible for all current and future development of PostgreSQL.
+ (scrappy@postgreSQL.org). (See below on how to join). This team is now
+ responsible for all current and future development of PostgreSQL.
The authors of PostgreSQL 1.01 were Andrew Yu and Jolly Chen. Many
others have contributed to the porting, testing, debugging and
1.2) What does PostgreSQL run on?
-
-
The authors have compiled and tested PostgreSQL on the following
platforms(some of these compiles require gcc 2.7.0):
* aix - IBM on AIX 3.2.5
* alpha - DEC Alpha AXP on OSF/1 2.0
* BSD44_derived - OSs derived from 4.4-lite BSD (NetBSD, FreeBSD)
- * bsdi - BSD/OS 2.0, 2.01, 2.1
+ * bsdi - BSD/OS 2.0, 2.01, 2.1, 3.0
* dgux - DG/UX 5.4R3.10
* hpux - HP PA-RISC on HP-UX 9.0
* i386_solaris - i386 Solaris
The following platforms have known problems/bugs:
* nextstep - Motorola MC68K or Intel x86 on NeXTSTEP 3.2
-
-
1.3) Where can I get PostgreSQL?
-
-
- The primary anonymous ftp site for PostgreSQL is:
+ The primary anonymous ftp site for PostgreSQL is:
* ftp://ftp.postgreSQL.org/pub
-
-
A mirror site exists at:
* ftp://postgres95.vnet.net/pub/postgres95
* ftp://ftp.luga.or.at/pub/postgres95
1.4) What's the copyright on PostgreSQL?
-
-
PostgreSQL is subject to the following COPYRIGHT.
PostgreSQL Data Base Management System
CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT,
UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
- 1.5) Support for PostgreSQL
+ 1.5) Support for PostgreSQL
-
-
There is no official support for PostgreSQL from the original
maintainers or from University of California, Berkeley. It is
maintained through volunteer effort only.
subscribe
end
-
-
to questions-request@postgreSQL.org.
There is also a digest list available. To subscribe to this list, send
with a BODY of:
-
subscribe
end
-
-
Additional information about PostgreSQL can be found via the
PostgreSQL WWW home page at:
http://postgreSQL.org
-
-
1.6) Latest release of PostgreSQL
-
-
The latest release of PostgreSQL is version 6.0, which was released on
- January 31, 1997. For information about what is new in 6.0, see our
- TODO list on our WWW page.
+ January 31, 1997. 6.1 is scheduled for release soon. For information
+ about what is new in 6.1, see our TODO list on our WWW page.
We expect a 7.0 release in several months that will remove time-travel
and reduce by 50% the size of on-disk system columns maintained for
1.7) Is there a commercial version of PostgreSQL?
-
-
Illustra Information Technology (a wholly owned subsidiary of Informix
Software, Inc.) sells an object-relational DBMS called Illustra that
was originally based on postgres. Illustra has cosmetic similarities
1.8) What documentation is available for PostgreSQL?
-
-
A user manual, manual pages, and some small test examples are included
in the distribution. The sql and built-in manual pages are
particularly important.
1.9) What version of SQL does PostgreSQL use?
-
-
PostgreSQL supports a subset of SQL-92. It has most of the important
constructs but lacks some of the functionality. The most visible
differences are:
* no support for nested subqueries
* no HAVING clause under a GROUP BY
-
-
On the other hand, you get to create user-defined types, functions,
inheritance etc. If you're willing to help with PostgreSQL coding,
eventually we can also add the missing features listed above.
1.10) Does PostgreSQL work with databases from earlier versions of postgres?
-
-
PostgreSQL v1.09 is compatible with databases created with v1.01.
Those upgrading from 1.0 should read the directions in the
MIGRATION_1.0_TO_1.02 directory.
1.11) How many people use PostgreSQL?
-
-
Since we don't have any licensing or registration scheme, it's
impossible to tell. We do know hundreds copies of PostgreSQL v1.* have
been downloaded, and that there many hundreds of subscribers to the
mailing lists.
-
_________________________________________________________________
-
-Section 2: Installation Questions
+
+Section 2: Installation Questions
-
-
2.1) initdb doesn't run
-
-
* check to see that you have the proper paths set
* check that the 'postgres' user owns all the right files
* ensure that there are files in $PGDATA/files, and that they are
non-empty. If they aren't, then "gmake install" failed for some
reason
-
-
2.2) when I start up the postmaster, I get "FindBackend: could not find a
backend to execute..." "postmaster: could not find backend to execute..."
-
-
You probably do not have the right path set up. The 'postgres'
executable needs to be in your path.
2.3) The system seems to be confused about commas, decimal points, and date
formats.
-
-
Check your locale configuration. PostgreSQL uses the locale settings
of the user that ran the postmaster process. Set those accordingly for
your operating environment.
2.4) How do I install PostgreSQL somewhere other than /usr/local/pgsql?
-
-
You need to edit Makefile.global and change POSTGRESDIR accordingly,
or create a Makefile.custom and define POSTGRESDIR there.
2.5) When I run postmaster, I get a Bad System Call core dumped message.
-
-
It could be a variety of problems, but first check to see that you
have system V extensions installed on your kernel. PostgreSQL requires
kernel support for shared memory.
2.6) I get the error message "obj/fmgr.h: No such file or directory"
-
-
This indicates that you did not generate the file fmgr.h properly.
Something failed in the running of the
src/backend/utils/Gen_fmgrtab.sh script. Check to see the paths used
2.7) When I try to start the postmaster, I get IpcMemoryCreate errors.
-
-
You either do not have shared memory configured properly in kernel or
you need to enlarge the shared memory available in the kernel. The
exact amount you need depends on your architecture and how many
2.8) I have changed a source file, but a recompile does not see the change?
-
-
The Makefiles do not have the proper dependencies for include files.
You have to do a 'make clean' and then another 'make'.
-
_________________________________________________________________
-
-Section 3: PostgreSQL Features
+
+Section 3: PostgreSQL Features
-
-
3.1) How do I specify a KEY or other constraints on a column?
-
-
Column constraints are not supported in PostgreSQL. As a consequence,
the system does not check for duplicates.
3.2) Does PostgreSQL support nested subqueries?
-
-
Subqueries are not implemented, but they can be simulated using sql
functions.
3.3) How do I define a unique indices?
-
-
PostgreSQL 6.0 supports unique indices.
3.4) I've having a lot of problems using rules.
-
-
Currently, the rule system in PostgreSQL is mostly broken. It works
enough to support the view mechanism, but that's about it. Use
PostgreSQL rules at your own peril.
3.5) I can't seem to write into the middle of large objects reliably.
-
-
The Inversion large object system in PostgreSQL is also mostly broken.
It works well enough for storing large wads of data and reading them
back out, but the implementation has some underlying problems. Use
3.6) Does PostgreSQL have a graphical user interface? A report generator? A
embedded query language interface?
-
-
No. No. No. Not in the official distribution at least. Some users have
reported some success at using 'pgbrowse' and 'onyx' as frontends to
PostgreSQL. Several contributions are working on tk based frontend
3.7) How can I write client applications to PostgreSQL?
-
-
PostgreSQL supports a C-callable library interface called libpq as
well as a Tcl-based library interface called libtcl.
3.8) How do I prevent other hosts from accessing my PostgreSQL backend?
-
-
Use host-based authentication by modifying the file $PGDATA/pg_hba
accordingly.
3.9) How do I set up a pg_group?
-
-
Currently, there is no easy interface to set up user groups. You have
to explicitly insert/update the pg_group table. For example:
CHANGE
jolly=>
-
-
The fields in pg_group are:
* groname: the group name. This a char16 and should be purely
alphanumeric. Do not include underscores or other punctuation.
* grolist: the list of pg_user id's that belong in the group. This
is an int4[].
-
-
3.10) What is the exact difference between binary cursors and normal cursors?
-
-
Normal cursors return data back in ASCII format. Since data is stored
natively in binary format, the system must do a conversion to produce
the ASCII format. In addition, ASCII formats are often large in size
3.11) Why doesn't the != operator work?
-
-
SQL specifies <> as the inequality operator, and that is what we have
defined for the built-in types.
3.12) What is a R-tree index and what is it used for?
-
-
An r-tree index is used for indexing spatial data. A hash index can't
handle range searches. A B-tree index only handles range searches in a
single dimension. R-tree's can handle multi-dimensional data. For
3.13) What is the maximum size for a tuple?
-
-
Tuples are limited to 8K bytes. Taking into account system attributes
and other overhead, one should stay well shy of 8,000 bytes to be on
the safe side. To use attributes larger than 8K, try using the large
3.14) I defined indices but my queries don't seem to make use of them. Why?
-
-
PostgreSQL does not automatically maintain statistics. One has to make
an explicit 'vacuum' call to update the statistics. After statistics
are updated, the optimizer has a better shot at using indices. Note
3.15) Are there ODBC drivers for PostgreSQL?
-
-
There are two ODBC drivers available, PostODBC and OpenLink ODBC.
For all people being interested in PostODBC, there are now two mailing
* postodbc-users@listserv.direct. net
* postodbc-developers@listse rv.direct.net
-
-
these lists are ordinary majordomo mailing lists. You can subscribe by
sending a mail to:
* majordomo@listserv.direct.net
-
-
OpenLink ODBC is currently in beta under Linux. You can get it from
http://www.openlinksw.com/postgres.html. It works with our standard
ODBC client software so you'll have Postgres ODBC available on every
3.16) How do I use postgres for multi-dimensional indexing (> 2 dimensions)?
-
-
Builtin R-Trees can handle polygons and boxes. In theory, R-trees can
be extended to handle higher number of dimensions. In practice,
extending R-trees require a bit of work and we don't currently have
3.17) How do I do regular expression searches? case-insensitive regexp
searching?
-
-
PostgreSQL supports the SQL LIKE syntax as well as more general
regular expression searching with the ~ operator. The !~ is the
negated regexp operator. ~* and !~* are the case-insensitive regular
3.18) I can't access the database as the 'root' user.
-
-
You should not create database users with user id 0(root). They will
be unable to access the database. This is a security precaution
because of the ability of any user to dynamically link object modules
3.19) I experienced a server crash during a vacuum. How do I remove the lock
file?
-
-
If the server crashes during a vacuum command, chances are it will
leave a lock file hanging around. Attempts to re-run the vacuum
command result in
WARN:can't create lock file -- another vacuum cleaner running?
-
-
If you are sure that no vacuum is actually running, you can remove the
file called "pg_vlock" in your database directory (which is
$PGDATA/base/<dbName>)
3.20) What is the difference between the various character types?
-
+
Type Internal Name Notes
--------------------------------------------------
CHAR char 1 character }
TEXT text length limited only by maximum tuple length
BYTEA bytea variable-length array of bytes
-
-
Remember, you need to use the internal name when creating indexes on
these fields or when doing other internal operations.
3.21) In a query, how do I detect if a field is NULL?
-
-
PostgreSQL has two builtin keywords, "isnull" and "notnull" (note no
spaces). Version 1.05 and later and 6.* understand IS NULL and IS NOT
NULL.
3.22) How do I see how the query optimizer is evaluating my query?
-
-
Place the word 'EXPLAIN' at the beginning of the query, for example:
-
EXPLAIN SELECT * FROM table1 WHERE age = 23;
-
-
3.23) How do I create a serial field?
-
-
Postgres does not allow the user to specifiy a user column as type
SERIAL. Instead, you can use each row's oid field as a unique value.
However, if you need to dump and reload the database, you need to be
Another valid way of doing this is to create a function:
-
create table my_oids (f1 int4);
insert into my_oids values (1);
create function new_oid () returns int4 as
'update my_oids set f1 = f1 + 1; select f1 from my_oids; '
language 'sql';
-
-
then:
-
create table my_stuff (my_key int4, value text);
insert into my_stuff values (new_oid(), 'hello');
-
-
However, keep in mind there is a race condition here where one server
could do the update, then another one do an update, and they both
could select the same new id. This statement should be performed
3.24) How do I create a multi-column index?
+ In 6.0, you can not directly create a multi-column index using create
+ index. You need to define a function which acts on the multiple
+ columns, then use create index with that function.
-
- You can not directly create a multi-column index using create index.
- You need to define a function which acts on the multiple columns, then
- use create index with that function.
+ In 6.1, this feature is available.
3.25) What are the temp_XXX files in my database directory?
-
-
They are temp_ files generated by the query executor. For example, if
a sort needs to be done to satisfy an ORDER BY, some temp files are
generated as a result of the sort.
3.26) Why are my table files not getting any smaller after a delete?
-
-
If you run vacuum in pre-6.0, unused rows will be marked for reuse,
but the file blocks are not released.
3.27) Why can't I connect to my database from another machine?
-
-
The default configuration allows only connections from tcp/ip host
localhost. You need to add a host entry to the file pgsql/data/pg_hba.
-
3.28) I get the error 'default index class unsupported' when creating an
index. How do I do it?
-
-
You probably used:
-
create index idx1 on person using btree (name);
-
-
PostgreSQL indexes are extensible, and therefore in pre-6.0, you must
specify a class_type when creating an index. Read the manual page for
create index (called create_index).
3.29) Why does creating an index crash the backend server?
-
-
You have probably defined an incorrect *_ops type class for the field
you are indexing.
3.30) How do I specify a decimal constant as a float8, or a string as a text?
Why am I getting poor precision?
-
-
Use the :: operator. It is needed only when the default promotion
rules fail. i.e.:
insert into tab1 values (4.23::float8, '2343'::text)
-
-
The default floating-point constant is a float4 in releases prior to
1.05. Later releases default to float8.
3.31) How do I find out what indexes or operations are defined in the
database?
-
-
Run the file pgsql/src/tutorial/syscat.source. It illustrates many of
the 'select's needed to get information out of the database system
tables.
3.32) My database is corrupt. I can't do anything. What should I do?
-
-
The 1.02 release has a README file and utility that describes a
possible cause of the problem and a workaround.
3.33) Createdb, destroydb, createuser,destroyuser don't run. Why?
-
-
Release 1.02 does not have this problem.
The 1.01 release of PostgreSQL uses a variable called PAGER to filter
'createuser' return 'unexpected last match in input()'? Why does pg_dump
fail?
-
-
You have compile postgres with flex version 2.5.3. There is bug in
this version of flex. Use flex version 2.5.2 or flex 2.5.4 instead.
There is a doc/README.flex file which will properly patch the flex
3.35) All my servers crash under concurrent table access. Why?
-
-
This problem can be caused by a kernel that is not configured to
support semaphores.
3.36) What tools are available for hooking postgres to Web pages?
-
-
For web integration, PHP/FI is an excellent interface. The URL for
that is http://www.vex.net/php/
An example of using WWW with C to talk to Postgres is can be tried at:
* http://postgreSQL.org/~mlc
-
-
An WWW gatway based on WDB using perl can be downloaded from:
* http://www.eol.ists.ca/~dunlop/wdb -p95
3.37) What is the time-warp feature and how does it relate to vacuum?
-
-
PostgreSQL handles data changes differently than most database
systems. When a row is changed in a table, the original row is marked
with the time it was changed, and a new row is created with the
SELECT *
FROM employees ['July 24, 1996 09:00:00']
-
-
displays employee rows in the table at the specified time. You can
specify intervals like [date,date], [date,], [,date], or [,]. This
last option accesses all rows that ever existed.
3.38) How do I tune the database engine for better performance?
-
-
There are two things that can be done. You can use Openlink's option
to disable fsync() by starting the postmaster with a '-o -F' option.
This will prevent fsync()'s from flushing to disk after every
3.39) What debugging features are available in PostgreSQL?
-
-
PostgreSQL has several features that report status information that
can be valuable for debugging purposes.
cd /usr/local/pgsql
./bin/postmaster >server.log 2>&1 &
-
-
This will put a server.log file in the top-level PostgreSQL directory.
This file can contain useful information about problems or errors
encountered by the server. Postmaster has a -d option that allows even
3.40) What is an oid? What is a tid?
-
-
Oids are Postgres's answer to unique row ids or serial columns. Every
row that is created in Postgres gets a unique oid. All oids generated
by initdb are less than 16384 (from backend/access/transam.h). All
3.41) What is the meaning of some of the terms used in Postgres?
-
-
Some of the source code and older documentation use terms that have
more common usage. Here are some:
* row, record, tuple
* portal, cursor
* range variable, table name, table alias
-
-
Please let me know if you think of any more.
3.42) What is Genetic Query Optimization?
-
-
The GEQO module in PostgreSQL is intended to solve the query
optimization problem of joining many tables by means of a Genetic
Algorithm (GA). It allows the handling of large join queries through
For further information see README.GEQO <utesch@aut.tu-freiberg.de>.
+ 3.43) I am running Solaris and my dates display wrong. Why?
+
+ Gcc under Solaris has an bug when compiled with optimization level 2.
+ Edit 'configure', and change -O2 to -O, and recompile. If 'configure'
+ does not exist in your top level source directory, make the change to
+ Makefile.global.
_________________________________________________________________
-
-Section 4: Extending PostgreSQL
+
+Section 4: Extending PostgreSQL
-
-
4.1) I wrote a user-defined function and when I run it in psql, it dumps
core.
-
-
The problem could be a number of things. Try testing your user-defined
function in a stand alone test program first. Also, make sure you are
not sending elog NOTICES when the front-end is expecting data, such as
4.2) I get messages of the type NOTICE:PortalHeapMemoryFree: 0x402251d0 not
in alloc set!
-
-
You are pfree'ing something that was not palloc'ed. When writing
user-defined functions, do not include the file "libpq-fe.h". Doing so
will cause your palloc to be a malloc instead of a free. Then, when
4.3) I've written some nifty new types and functions for PostgreSQL.
-
-
Please share them with other PostgreSQL users. Send your extensions to
mailing list, and they will eventually end up in the contrib/
subdirectory.
4.4) How do I write a C function to return a tuple?
-
-
This requires extreme wizardry, so extreme that the authors have not
ever tried it, though in principle it can be done. The short answer is
... you can't. This capability is forthcoming in the future.
-
_________________________________________________________________
-
-Section 5: Bugs
+
+Section 5: Bugs
-
-
5.1) How do I make a bug report?
-
-
Check the current FAQ at http://postgreSQL.org
Also check out our ftp site ftp://ftp.postgreSQL.org/pub to see if
You can also fill out the "bug-template" file and send it to:
* bugs@postgreSQL.org
-
-
This is the address of the developers mailing list.
====================================================
TODO list (FAQ) for PostgreSQL
====================================================
-last updated: Sat Mar 1 21:28:10 EST 1997
+last updated: Tue May 13 23:16:50 EDT 1997
current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
The most recent version of this document can be viewed at
the postgreSQL WWW site, http://www.postgreSQL.org.
-Changes included in the 6.0 release are listed at the end of this page.
+Dashed items(-) are being worked on for the 6.1 release.
-Dashed items(-) are being worked on for the post-6.0 release.
+THE CHANGES FOR 6.1 APPEAR AT THE END OF THIS DOCUMENT
Developers who have claimed items are:
Bruce is Bruce Momjian<maillist@candle.pha.pa.us>
Darren is Darren King <darrenk@insightdist.com>
Edmund is Edmund Mergl <E.Mergl@bawue.de>
Erich Stamberger <eberger@gewi.kfunigraz.ac.at>
+ Jun is Jun Kuwamura <juk@rccm.co.jp>
Kurt is "Kurt J. Lidl" <lidl@va.pubnix.com>
Martin is Martin S. Utesch <utesch@aut.tu-freiberg.de>
+ Oleg is Oleg Bartunov <oleg@sai.msu.su>
+ Paul is Paul M. Aoki <aoki@CS.Berkeley.EDU>
+ Raymond is Raymond Toy <toy@rtp.ericsson.se>
+ Soo-Ho Ok <shok@detc.dongeui-tc.ac.kr>
+ Stefan Simkovics <ssimkovi@rainbow.studorg.tuwien.ac.at>
+ Sven is Sven Verdoolaege <skimo@breughel.ufsia.ac.be>
Thomas is Thomas Lockhart <tgl@mythos.jpl.nasa.gov>
Vadim is "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
Vivek is Vivek Khera <khera@kci.kciLink.com>
ENHANCEMENTS
------------
-Add full ANSI SQL capabilities
+Add full ANSI SQL capabilities (Stefan)
add subselects, possibility using temporary SQL functions
Implement HAVING clause
Implement EXISTS qualifier
add the concept of dataspaces
allow conversion type casts on SELECT target fields
Allow compression of large fields or a compressed field type
-Fix the rules system(Jan?)
+Fix the rules system(Jan?,Soo-Ho)
robust
making INSTEAD rules work
add CONSTRAINT
Full set of text operations and functions
- word searches, concat, upper/lower(), max() on text, char
+- upper/lower()
+ word searches, concat,max() on text, char
Replace table-level locking with row or page-level locking(Vadim)
Large objects
overwriting blocks has problems
Fix large object mapping scheme
not to stuff everything as files in a single directory
Better interface for adding to pg_group
-Make multi-field indexes easier to create
+-Make multi-field indexes easier to create(Vadim)
allow optimizer to effectively use parameters without accessing table
-Add int8 type
-Add MONEY/DECIMAL type with defined precision
-Add table comments
+-Add int8 type(Thomas)
+-Add MONEY/DECIMAL type(Thomas)
+Make MONEY/DECIMAL have a defined precision
Add support for tables >2G, or test current version
Incorporate the PERL PG95 interface library into source tree(Edmund)
Threaded version of the server or libpq
reduce system column overhead(Vadmin)
remove pg_time table(Vadim)
allow row re-use without vacuum, maybe?(Vadim)
-split apart row removal function from statistics function
+-split apart row removal function from statistics function(Vadim)
can't vacuum large objects
+can't reduce index file size with vacuum
Remove restriction that ORDER BY field must be in SELECT list(?)
Allow queries about owner of datbases, tables like:
SELECT u.usesysid FROM postgres.pg_user u;
Add command to show privileges
Allow INSERT INTO ... SELECT to convert column types
Add syslog functionality
-Allow aggregate for All types, like count(Darren)
+Allow aggregate for all types, like count(Darren)
Improve optimizer plan choice(Darren)
Add STDDEV/VARIANCE() function for standard deviation computation/variance
-Add upper/lower functions
Add table/column/function discription table indexed by oid
-make all identifiers case-insensitive(Bruce)
add pg_type attribute to identify types that need length (bpchar, varchar)
add UNIQUE capability to non-btree indexes
-allow GROUP BY on columns that are functions
-add non-ascii collating strings with strcoll() and setlocale()
-new DATE routines (Thomas)
+-allow GROUP BY on columns that on functions(Vadim)
+-add non-ascii collating strings with strcoll() and setlocale (Oleg)
+-new DATE routines (Thomas)
+-index NULL fields(Vadim)
+-Add SERIAL column type(Vadim)
+-Add multi-column indexes(Vadim)
+-Add SET VAR TO command
PERFORMANCE
-----------
DOCUMENTATION
-------------
-Update usermanual source
+Update usermanual source(many)
remove time-travel in documentation(Bruce)
added features used in grammer but not in docs, like :: and CAST
add DECLARE manual page
PORTABILITY
-----------
Change c.h "Index" and "bool" so they do not conflict with c++
-
+
---------------------------------------------------------------------------
- CHANGES IN 6.0 RELEASE
-Bug Fixes
----------
-ALTER TABLE bug - running postgress process needs to re-read table definition
-Allow vacuum to be run on one table or entire database(Bruce)
-Array fixes
-Fix array over-runs of memory writes(Kurt)
-Fix elusive btree range/non-range bug(Dan)
-Fix for hash indexes on some types like time and date
-Fix for pg_log size explosion
-Fix permissions on lo_export()(Bruce)
-Fix unitialized reads of memory(Kurt)
-Fixed ALTER TABLE ... char(3) bug(Bruce)
-Fixed a few small memory leaks
-Fixed EXPLAIN handling of options and changed full_path option name
-Fixed output of group acl permissions
-Memory leaks (hunt and destroy with tools like Purify(Kurt)
-Minor improvements to rules system
-NOTIFY fixes
-New asserts for run-checking
-Overhauled parser/analyze code to properly report errors and increase speed
-Pg_dump -d now handles NULL's properly(Bruce)
-Prevent SELECT NULL from crashing server (Bruce)
-Properly report errors when INSERT ... SELECT columns did not match
-Properly report errors when insert column names were not correct
-Psql \g filename now works(Bruce)
-Psql fixed problem with multiple statements on one line with multiple outputs
-Removed duplicate system oid's
-SELECT * INTO TABLE . GROUP/ORDER BY gives unlink error if table exists(Bruce)
-Several fixes for queries that crashed the backend
-Starting quote in insert string errors(Bruce)
-Submiting an empty query now returns empty status, not just " " query(Bruce)
+ CHANGES IN THE 6.1 RELEASE
-Enhancements
-------------
-Add EXPLAIN manual page(Bruce)
-Add UNIQUE index capability(Dan)
-Add hostname/user level access control rather than just hostname and user
-Add synonym of != for <>(Bruce)
-Allow "select oid,* from table"
-Allow BY,ORDER BY to specify columns by number, or by non-alias table.column(Bruce)
-Allow COPY from the frontend(Bryan)
-Allow GROUP BY to use alias column name(Bruce)
-Allow actual compression, not just reuse on the same page(Vadim)
-Allow installation-configuration option to auto-add all local users(Bryan)
-Allow libpq to distinguish between text value '' and null(Bruce)
-Allow non-postgres users with createdb privs to destroydb's
-Allow restriction on who can create C functions(Bryan)
-Allow restriction on who can do backend COPY(Bryan)
-Allow system to use oid index using constant without cast to oid(Bruce)
-Auto-cast numeric constants to type of non-constant(Bruce)
-Can shrink tables, pg_time and pg_log(Vadim & Erich)
-Change debug level 2 to print queries only, changed debug heading layout(Bruce)
-Change default decimal constant representation from float4 to float8(Bruce)
-European date format now set when postmaster is started
-Execute lowercase function names if not found with exact case
-Fixes for aggregate/GROUP processing, allow 'select sum(func(x),sum(x+y) from z'
-Gist now included in the distrubution(Marc)
-Idend authentication of local users(Bryan)
-Implement BETWEEN qualifier(Bruce)
-Implement IN qualifier(Bruce)
-Libpq has PQgetisnull()(Bruce)
-Libpq++ improvements
-New options to initdb(Bryan)
-Pg_dump allow dump of oid's(Bruce)
-Pg_dump create indexes after tables are loaded for speed(Bruce)
-Pg_dumpall dumps all databases, and the user table
-Pginterface additions for NULL values(Bruce)
-Prevent postmaster from being run as root
-Psql \h and \? is now readable(Bruce)
-Psql allow backslashed, semicolons anywhere on the line(Bruce)
-Psql changed command prompt for lines in query or in quotes(Bruce)
-Psql char(3) now displays as (bp)char in \d output(Bruce)
-Psql return code now more accurate(Bryan?)
-Psql updated help syntax(Bruce)
-Re-visit and fix vacuum(Vadim)
-Reduce size of regression diffs, remove timezone name difference(Bruce)
-Remove compile-time parameters to enable binary distributions(Bryan)
-Reverse meaning of HBA masks(Bryan)
-Secure Authentication of local users(Bryan)
-Speed up vacuum(Vadim)
-Vacuum now had VERBOSE option(Bruce)
+new configuration script(Marc)
+readline configuration option added(Marc)
+OS-specific configuration options removed(Marc)
+new OS-specific template files(Marc)
+no more need to edit Makefile.global(Marc)
+attribute optimization statistics(Bruce)
+re-arrange include files(Marc)
+much faster new btree bulk load code(Paul)
+BTREE UNIQUE added to bulk load code(Vadim)
+new lock debug code(Massimo)
+packet length checking in library routines
+lock manager priority patch
+massing changes to libpg++(Leo)
+nextstep patches (Gregor Hoffleit)
+removed WIN32-specific code(Bruce)
+new GEQO optimizer speeds table multi-table optimization(Martin)
+removed postmaster -e option, now only postgres -e option (Bruce)
+check for under/over flow of float8(Bruce)
+multi-table join fix(Vadim)
+new WARN message for non-unique insert into unique key(Marc)
+update x=-3, no spaces, now valid(Bruce)
+remove case-sensitive identifier handling(Bruce,Thomas,Dan)
+SIGPIPE crash fix(Darren)
+debug backend now pretty-prints tree(Darren)
+new Oracle character functions(Edmund)
+new plaintext password functions(Dan)
+no such class or insufficient privilege changed to distinct messages(Dan)
+new ANSI timestamp function(Dan)
+new ANSI Time and Date types (Thomas)
+merge duplicate library code in front/backends(Martin)
+move large chunks of data in backend(Martin)
+multi-column btree indexes(Vadim)
+new SET var TO value command(Martin)
+now works with eBones, international Kerberos(Jun)
+large object fixes(Sven)
+allow btree indexes to handle NULLs(Vadim)
+timezone fixes(D'Arcy)
+more shared library support
+auto-udpate transaction status on reads(Dan)
+new locale settings for character types(Oleg)
+new SEQUENCE serial number generator(Vadim)
+select SUM(x) can return NULL on no rows(Thomas)
+internal optimizer, executor bug fixes(Vadim)
+fix problem where inner loop in < or <= has no rows(Vadim)
+prevent re-commuting join index clauses(Vadim)
+fix join clauses for multiple tables(Vadim)
+fix hash, hashjoin for arrays(Vadim)
+fix btree for abstime type(Vadim)
+GROUP BY function now possible(Vadim)
+re-organize regression test(Thomas,Marc)
+new optimizer operation weights(Vadim)
+new psql \z grant/permit option(Marc)
+new MONEY data type(D'Arcy)
+c++ include file cleanup(Bruce)
+tcp socket communication speed improved(Vadim)
+large object fixes(Raymond)
+new VACUUM option for attribute statistics, and for certain columns (Vadim)
+many geometric type improvements(Thomas,Keith)
+additional regression tests(Thomas)
+new datestyle variable(Thomas)
+more comparison operators for sorting types(Thomas)
+new conversion functions(Thomas)
+new more compact btree format(Vadim)
-Source tree changes
--------------------
-All functions now have prototypes that are compared against the calls
-Allow asserts to be disabled easly from Makefile.global(Bruce)
-Change oid constants used in code to #define names
-Decoupled sparc and solaris defines(Kurt)
-Gcc -Wall compiles cleanly with warnings only from unfixable constructs
-Major include file reorganization/reduction(Marc)
-Make now stops on compile failure(Bryan)
-Makefile restructuring(Bryan, Marc)
-Merge bsdi_2_1 to bsdi(Bruce)
-Monitor program removed
-Name change from Postgres95 to PostgreSQL
-New config.h file(Marc, Bryan)
-PG_VERSION now set to 6.0 and used by postmaster
-Portability additions, including Ultrix, DG/UX, AIX, and Solaris
-Reduced the number of #define's, centeralized #define's
-Remove duplicate OIDS in system tables(Dan)
-Remove duplicate system catalog info or report mismatches(Dan)
-Removed many os-specific #define's
-Restructured object file generation/location(Bryan, Marc)
-Restructured port-specific file locations(Bryan, Marc)
-Unused/uninialized variables corrected
OSDN Git Service
