Update files and dates for 6.1.1 release.
This commit is contained in:
parent
41b805b913
commit
b6d983559a
2
HISTORY
2
HISTORY
@ -1,4 +1,4 @@
|
||||
PostgreSQL 6.1.1 Sun Jul 13 15:11:47 EDT 1997
|
||||
PostgreSQL 6.1.1 Mon Jul 22 18:04:49 EDT 1997
|
||||
-------------------------------------------------------------
|
||||
|
||||
This release does NOT require a dump/restore for those running 6.1.
|
||||
|
17
doc/FAQ
17
doc/FAQ
@ -1,7 +1,7 @@
|
||||
|
||||
Frequently Asked Questions (FAQ) for PostgreSQL
|
||||
|
||||
Last updated: Mon Jul 14 12:27:39 EDT 1997
|
||||
Last updated: Mon Jul 21 18:04:00 EDT 1997
|
||||
Version: 6.1.1
|
||||
|
||||
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
|
||||
@ -255,9 +255,9 @@ Section 1: General Questions
|
||||
|
||||
1.6) Latest release of PostgreSQL
|
||||
|
||||
The latest release of PostgreSQL is version 6.1.1, which will be
|
||||
released in July, 1997. For information about what is new in 6.1.1,
|
||||
see our TODO list on our WWW page.
|
||||
The latest release of PostgreSQL is version 6.1.1, which was released
|
||||
on July 22, 1997. For information about what is new in 6.1.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
|
||||
@ -304,9 +304,10 @@ Section 1: General Questions
|
||||
|
||||
Upgrading to 6.1 requires a dump and restore from previous releases.
|
||||
|
||||
Upgrading from 6.1 to 6.1.1 requires a compile of the new release,
|
||||
recompile of all your custom applications to use the new libpq, and
|
||||
then an install while the postmaster is temporarily stopped.
|
||||
Upgrading from 6.1 to 6.1.1 requires running configure, compile of the
|
||||
new release, recompile of all your custom applications to use the new
|
||||
libpq, and then an install while the postmaster is temporarily
|
||||
stopped.
|
||||
|
||||
Those ugrading from versions earlier than 1.09 must upgrade to 1.09
|
||||
first without a dump/reload, then dump the data from 1.09, and then
|
||||
@ -647,7 +648,7 @@ BYTEA bytea variable-length array of bytes
|
||||
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.
|
||||
This feature is available in 6.1 and later releases.
|
||||
|
||||
3.25) What are the temp_XXX files in my database directory?
|
||||
|
||||
|
3
doc/TODO
3
doc/TODO
@ -1,7 +1,7 @@
|
||||
====================================================
|
||||
TODO list (FAQ) for PostgreSQL
|
||||
====================================================
|
||||
last updated: Sun Jul 13 23:13:24 EDT 1997
|
||||
last updated: Mon Jul 21 18:01:37 EDT 1997
|
||||
|
||||
current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
|
||||
|
||||
@ -128,6 +128,7 @@ make number of backends a config parameter, storage/sinvaladt.h:MaxBackendId
|
||||
certain indexes will not shrink, i.e. oid indexes with many inserts
|
||||
make NULL's come out at the beginning or end depending on the ORDER BY direction
|
||||
change the library/backend interface to use network byte order
|
||||
allow unix domain sockets for local connections for performance and security
|
||||
|
||||
PERFORMANCE
|
||||
-----------
|
||||
|
Loading…
x
Reference in New Issue
Block a user