Skip to content

Commit 973a037

Browse files
committed
Update README, HISTORY, etc for beta release.
1 parent ba0b03d commit 973a037

File tree

6 files changed

+154
-77
lines changed

6 files changed

+154
-77
lines changed

HISTORY

+105
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,108 @@
1+
PostgreSQL 6.2beta Sat Sep 13 21:53:27 EDT 1997
2+
-------------------------------------------------------------
3+
4+
A dump/restore is required for those wishing to migrate data from
5+
previous releases of PostgreSQL.
6+
7+
Bug Fixes
8+
---------
9+
Fix problems with pg_dump for iheritance, sequences, archive tables(Bruce)
10+
Fix compile errors on overflow due to shifts, unsigned, and bad prototypes
11+
from Solaris, (Diab Jerius)
12+
Fix bugs in line arithmetic which resulted in bad intersection
13+
calculations(Thomas)
14+
Check explicitly for intersections at endpoints to avoid rounding
15+
ugliness(Thomas)
16+
Catch non-functional delete attempts(Vadim)
17+
Change time function names to be more consistent(Michael Reifenberg)
18+
Check for zero divides(Michael Reifenberg)
19+
Fix very old bug which made tuples changed/inserted by a commnd
20+
visible to command itself (so we had multiple update of
21+
updated tuples, etc).(Vadim)
22+
Fix for SELECT null, 'fail' FROM pg_am (Patrick)
23+
SELECT NULL as EMPTY_FIELD now allowed(Patrick)
24+
25+
Enhancements
26+
------------
27+
psql: Add PAGER for \h and \?,\C fix
28+
Allow hh:mm:ss time entry for timespan/reltime types(Thomas)
29+
Add center() routines for lseg, path, polygon(Thomas)
30+
Add distance() routines for circle-polygon, polygon-polygon(Thomas)
31+
Check explicitly for points and polygons contained within polygons
32+
using an axis-crossing algorithm. (Thomas)
33+
Add routine to convert circle-box(Thomas)
34+
Merge conflicting operators for different geometric data types
35+
(the point type especially had operators which were
36+
weirdly dissimilar from the other types)(Thomas)
37+
Replace distance operator "<===>" with "<->"(Thomas)
38+
Replace "above" operator "!^" with ">^"
39+
and "below" operator "!|" with "<^"(Thomas)
40+
Add routines for text trimming on both ends, substring, and string position(Thomas)
41+
Add new operators and functions for geometric types(Thomas)
42+
Add text concatenation operator and function(Thomas)
43+
Add text trim function for SQL92 support(Thomas)
44+
Added conversion routines circle(box) and poly(circle)(Thomas)
45+
Use better routines from geometry library(Thomas)
46+
Allow use parameters in target list having aggregates in functions(Vadim)
47+
Allow internal sorts to be stored in memory rather than in files(Bruce)
48+
Added JDBC driver as an interface(Adrian & Peter)
49+
Reduce open() calls(Bruce)
50+
NOT NULL implementation (Robson Paniago de Miranda).
51+
CHECK/DEFAULT syntax(Vadim)
52+
Syntax for [CONSTRAINT name] CHECK ...(Vadim)
53+
Allow functions and operators on internally-identical types to succeed(Bruce)
54+
Speed up backend startup after profiling analysis(Bruce)
55+
pg_password utility
56+
Number of tuples inserted/affected by INSERT/UPDATE/DELETE...(Vadim)
57+
SPI manager(Vadim)
58+
Triggers (Vadim)
59+
Add detection and warnings for UNION and HAVING clauses(Thomas)
60+
Add more reserved words, mostly for SQL92 compliance(Thomas)
61+
Include reserved words for string handling, outer joins, and unions(Thomas)
62+
Implement extended comments ("/* ... */") using exclusive states(Thomas)
63+
Modify definitions of operators to remove some restrictions on characters
64+
and character order(Thomas)
65+
Fix for psql pager when no tty(Bruce)
66+
Add // comments(Bruce)
67+
New entab utility(Bruce)
68+
New system relations to store DEFAULT/CHECK expressions(Vadim)
69+
Store CHECK infos on CREATE TABLE(Vadim)
70+
Default GEQO parameter is now 8(Bruce)
71+
Define DOUBLE PRECISION, INTERVAL, CHARACTER, and
72+
CHARACTER VARYING (SQL-92)(Thomas)
73+
Define EXTRACT(), POSITION(), SUBSTRING(), and TRIM() (SQL-92)(Thomas)
74+
75+
Source Tree Changes
76+
-------------------
77+
HPUX 10 patches (Vladimir Turin)
78+
Added SCO support, (Daniel Harris)
79+
mkLinux patches (Tatsuo Ishii)
80+
Change box terminology from "length" to "width"(Thomas)
81+
Deprecate temporary unstored slope fields(Thomas)
82+
Remove restart instructions from INSTALL(Bruce)
83+
Look in /usr/ucb first for install(Bruce)
84+
Fix c++ copy example code(Thomas)
85+
Add -o to psql manual page(Bruce)
86+
Prevent relname unallocated string length from being copied into database(Bruce)
87+
Cleanup for NAMEDATALEN use(Bruce)
88+
Fix pgproc names over 15 chars in output(Bruce)
89+
Add strNcpy() function(Bruce)
90+
remove some (void) casts that are unnecessary(Bruce)
91+
new interfaces directory(Marc)
92+
Replace fopen() calls with calls to fd.c functions(Bruce)
93+
Make functions static where possible(Bruce)
94+
enclose unused functions in #ifdef NOT_USED(Bruce)
95+
Fix for sunos4 difftime() call(Bruce)
96+
Changes for Digital Unix
97+
Portability fix for pg_dumpall(Bruce)
98+
Rename pg_attribute.attnvals to attdisbursion(Bruce)
99+
intro/unix manual page now pgintro(Bruce)
100+
built-in manual page now pgbuiltin(Bruce)
101+
Add PGINDENT and support program(Bruce)
102+
Massive commit to run PGINDENT on all *.c and *.h files(Bruce)
103+
Files moved to /src/tools directory(Bruce)
104+
105+
1106
PostgreSQL 6.1.1 Mon Jul 22 18:04:49 EDT 1997
2107
-------------------------------------------------------------
3108

INSTALL

+10-19
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ POSTGRESQL INSTALLATION INSTRUCTIONS
22
Copyright (c) 1997 Regents of the University of California
33

44
This is file /usr/src/pgsql/INSTALL. It contains notes on how to install
5-
PostgreSQL v6.1.1. Up to date information on PostgreSQL may be found at
5+
PostgreSQL v6.2. Up to date information on PostgreSQL may be found at
66
http://www.postgresql.org.
77

88
PostgreSQL is an RDBMS database server. It is not completely ANSI SQL
@@ -69,17 +69,8 @@ You should have at least 8 MB of memory and at least 45 MB of disk space
6969
to hold the source, binaries, and user databases. After installation
7070
you may reduce this to about 3 Mbytes plus space for user databases.
7171

72-
To upgrade from PostgreSQL v6.1 to v6.1.1 do the following:
73-
-----------------------------------------------------------
74-
1) Run configure on the new release
75-
2) Compile the new release
76-
3) Recompile your custom applications to use the new libpq library
77-
4) Stop the postmaster
78-
5) Install the new release
79-
6) Restart the postmaster
80-
81-
To those doing a fresh install or upgrading to PostgreSQL v6.1.1
82-
from 6.0 or 1.* release, do the following:
72+
To those doing a fresh install or upgrading from previous releases of
73+
PostgreSQL:
8374
----------------------------------------------
8475

8576
1) Read any last minute information and platform specific porting
@@ -120,7 +111,7 @@ from 6.0 or 1.* release, do the following:
120111

121112
To check for disk space, use command "df -k".
122113

123-
4) Ftp file ftp://ftp.postgresql.org/pub/postgresql-v6.1.1.tar.gz from the
114+
4) Ftp file ftp://ftp.postgresql.org/pub/postgresql-v6.2.tar.gz from the
124115
internet. Store it in your home directory.
125116

126117
5) Some platforms use flex. If your system uses flex then make sure
@@ -162,7 +153,7 @@ from 6.0 or 1.* release, do the following:
162153
postgres super user. Type (with the gunzip line and the following
163154
line typed as one line):
164155
cd
165-
gunzip -c postgresql-v6.1.1.tar.gz |
156+
gunzip -c postgresql-v6.2.tar.gz |
166157
tar xvf - src/bin/pg_dump/pg_dumpall
167158
chmod a+x src/bin/pg_dump/pg_dumpall
168159
src/bin/pg_dump/pg_dumpall > db.out
@@ -227,7 +218,7 @@ from 6.0 or 1.* release, do the following:
227218

228219
10) Unzip and untar the new source file. Type
229220
cd /usr/src/pgsql
230-
gunzip -c ~/postgresql-v6.1.1.tar.gz | tar xvf -
221+
gunzip -c ~/postgresql-v6.2.tar.gz | tar xvf -
231222

232223
11) Configure the source code for your system. It is this step at which
233224
you can specify your actual source path and installation paths for
@@ -419,10 +410,10 @@ from 6.0 or 1.* release, do the following:
419410

420411
Here is an example from a i686/Linux-ELF platform (this is the platform
421412
on which most of the regression tests were generated). No tests failed
422-
since this is the v6.1.1 regression reference platform.
413+
since this is the v6.2 regression reference platform.
423414

424415
Here is an example from the SPARC/Linux-ELF platform. Using the
425-
970525 beta version of PostgreSQL v6.1.1 the following tests "failed".
416+
970525 beta version of PostgreSQL v6.2 the following tests "failed".
426417
float8 and geometry "failed" due to minor precision differences in
427418
floating point numbers. select_views produces massively different output,
428419
but the differences are due to minor floating point differences.
@@ -547,7 +538,7 @@ from 6.0 or 1.* release, do the following:
547538
rm -rf /usr/local/pgsql_6_0
548539
# Also delete old database directory tree if it is not in
549540
# /usr/local/pgsql_6_0/data
550-
rm ~/postgresql-v6.1.1.tar.gz
541+
rm ~/postgresql-v6.2.tar.gz
551542

552543
26) You will probably want to print out the documentation. Here is how
553544
you might do it if you have Ghostscript on your system and are
@@ -574,7 +565,7 @@ from 6.0 or 1.* release, do the following:
574565
supported platforms. We therefore ask you to let us know if you did
575566
or did not get PostgreSQL to work on you system. Please send a
576567
mail message to [email protected] telling us the following:
577-
- The version of PostgreSQL (v6.1, 6.1.1, beta 970703, etc.).
568+
- The version of PostgreSQL (v6.2, 6.1.1, beta 970703, etc.).
578569
- Your operating system (i.e. RedHat v4.0 Linux v2.0.26).
579570
- Your hardware (SPARC, i486, etc.).
580571
- Did you compile, install and run the regression tests cleanly?

README

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL Data Base Management System (formerly known as Postgres, then
33
as Postgres95).
44

5-
This directory contains the version 6.1 release of the PostgreSQL
5+
This directory contains the version 6.2 release of the PostgreSQL
66
database server. The server is not ANSI SQL compliant, but it gets
77
closer with every release. After you unzip and untar the distribution
88
file, look at file INSTALL for the installation notes and file HISTORY

doc/FAQ

+20-40
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Thu Sep 4 01:32:22 EDT 1997
5-
Version: 6.1.1
4+
Last updated: Sat Sep 13 22:00:02 EDT 1997
5+
Version: 6.2beta
66

77
Current maintainer: Bruce Momjian ([email protected])
88

@@ -90,6 +90,7 @@ Questions answered:
9090
3.21) What is the meaning of some of the terms used in Postgres?
9191
3.22) What is Genetic Query Optimization?
9292
3.23) How do you remove a column from a table?
93+
3.24) How do SELECT only the first few rows of a query?
9394

9495
4) Questions about extending PostgreSQL
9596

@@ -514,24 +515,7 @@ Section 3: PostgreSQL Features
514515

515516
3.6) What is the exact difference between binary cursors and normal cursors?
516517

517-
Normal cursors return data back in ASCII format. Since data is stored
518-
natively in binary format, the system must do a conversion to produce
519-
the ASCII format. In addition, ASCII formats are often large in size
520-
than binary format. Once the attributes come back in ASCII, often the
521-
client application then has to convert it to a binary format to
522-
manipulate it anyway.
523-
524-
Binary cursors give you back the data in the native binary
525-
representation. Thus, binary cursors will tend to be a little faster
526-
since there's less overhead of conversion.
527-
528-
However, ASCII is architectural neutral whereas binary representation
529-
can differ between different machine architecture. Thus, if your
530-
client machine uses a different representation than you server
531-
machine, getting back attributes in binary format is probably not what
532-
you want. Also, if your main purpose is displaying the data in ASCII,
533-
then getting it back in ASCII will save you some effort on the client
534-
side.
518+
See the declare manual page for a description.
535519

536520
3.7) What is a R-tree index and what is it used for?
537521

@@ -590,24 +574,12 @@ Section 3: PostgreSQL Features
590574
3.10) How do I do regular expression searches? case-insensitive regexp
591575
searching?
592576

593-
PostgreSQL supports the SQL LIKE syntax as well as more general
594-
regular expression searching with the ~ operator. The !~ is the
595-
negated regexp operator. ~* and !~* are the case-insensitive regular
596-
expression operators.
577+
See the pgbuiltin manual page. Search for regular expression.
597578

598579
3.11) I experienced a server crash during a vacuum. How do I remove the lock
599580
file?
600581

601-
If the server crashes during a vacuum command, chances are it will
602-
leave a lock file hanging around. Attempts to re-run the vacuum
603-
command result in
604-
605-
606-
WARN:can't create lock file -- another vacuum cleaner running?
607-
608-
If you are sure that no vacuum is actually running, you can remove the
609-
file called "pg_vlock" in your database directory (which is
610-
$PGDATA/base/<dbName>)
582+
See the vacuum manual page.
611583

612584
3.12) What is the difference between the various character types?
613585

@@ -638,10 +610,8 @@ BYTEA bytea variable-length array of bytes
638610

639611
3.14) How do I see how the query optimizer is evaluating my query?
640612

641-
Place the word 'EXPLAIN' at the beginning of the query, for example:
642-
643-
EXPLAIN SELECT * FROM table1 WHERE age = 23;
644-
613+
See the explain manual page.
614+
645615
3.15) How do I create a serial field?
646616

647617
Postgres does not allow the user to specifiy a user column as type
@@ -683,6 +653,7 @@ BYTEA bytea variable-length array of bytes
683653

684654
The default configuration allows only connections from tcp/ip host
685655
localhost. You need to add a host entry to the file pgsql/data/pg_hba.
656+
See the hba_conf manual page.
686657

687658
3.18) How do I find out what indexes or operations are defined in the
688659
database?
@@ -769,11 +740,20 @@ BYTEA bytea variable-length array of bytes
769740

770741
We do not support ALTER TABLE DROP COLUMN, but do this:
771742

772-
SELECT ... # select all columns but the one you want to remove
743+
SELECT ... -- select all columns but the one you want to remove
773744
INTO TABLE new_table
774745
FROM old_table;
775746
DROP TABLE old_table;
776747
ALTER TABLE new_table RENAME TO old_table;
748+
749+
3.23) How do SELECT only the first few rows of a query?
750+
751+
See the fetch manual page.
752+
753+
This only prevents all row results from being transfered to the
754+
client. The entire query must be evaluated, even if you only want just
755+
first few rows. Consider a query that has and ORDER BY. There is no
756+
way to return any rows until the entire query is evaluated and sorted.
777757
_________________________________________________________________
778758

779759
Section 4: Extending PostgreSQL
@@ -819,4 +799,4 @@ Section 5: Bugs
819799
You can also fill out the "bug-template" file and send it to:
820800
821801

822-
This is the address of the developers mailing list.
802+
This is the address of the developers mailing list.

0 commit comments

Comments
 (0)