Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit a654db3

Browse files
committedFeb 1, 1998
Upgrade doc stuff to 6.3.
1 parent 6159ba3 commit a654db3

File tree

7 files changed

+494
-218
lines changed

7 files changed

+494
-218
lines changed
 

‎HISTORY

Lines changed: 163 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,166 @@
1+
PostgreSQL 6.3 Sun Feb 1 14:57:30 EST 1998
2+
-------------------------------------------------------------
3+
4+
A dump/restore is required for those wishing to migrate data from
5+
previous releases of PostgreSQL.
6+
7+
CHANGES IN THE 6.3 RELEASE
8+
--------------------------
9+
10+
Bug Fixes
11+
---------
12+
Fix binary cursors broken by MOVE implementation(Vadim)
13+
Fix for tcl library crash(Jan)
14+
Fix for array handling, from Gerhard Hintermayer
15+
Fix acl error, and remove duplicate pqtrace(Bruce)
16+
Fix psql \e for empty file(Bruce)
17+
Fix for textcat on varchar() fields(Bruce)
18+
Fix for DBT Sendproc (Zeugswetter Andres)
19+
Fix vacuum analyze syntax problem(Bruce)
20+
Fix for international identifiers(Tatsuo)
21+
Fix aggregates on inherited tables(Bruce)
22+
Fix substr() for out-of-bounds data
23+
Fix for select 1=1 or 2=2, select 1=1 and 2=2, and select sum(2+2)(Bruce)
24+
Fix notty output to show status result. -q option still turns it off(Bruce)
25+
Fix for count(*), aggs with views and multiple tables and sum(3)(Bruce)
26+
Fix cluster(Bruce)
27+
Fix for PQtrace start/stop several times(Bruce)
28+
Fix a variety of locking problems like newer lock waiters getting
29+
lock before older waiters, and having readlock people not share
30+
locks if a writer is waiting for a lock, and waiting writers not
31+
getting priority over waiting readers(Bruce)
32+
Fix crashes in psql when executing queries from external files(James)
33+
Fix problem with multiple order by columns, with the first one having
34+
NULL values(Jeroen)
35+
Use correct hash table support functions for float8 and int4(Thomas)
36+
Re-enable JOIN= option in CREATE OPERATOR statement (Thomas)
37+
Change precedence for boolean operators to match expected behavior(Thomas)
38+
Generate elog(ERROR) on over-large integer(Bruce)
39+
Allow multiple-argument functions in constraint clauses(Thomas)
40+
Check boolean input literals for 'true','false','yes','no','1','0'
41+
and throw elog(ERROR) if unrecognized(Thomas)
42+
43+
44+
Enhancements
45+
------------
46+
Real deadlock detection, no more timeouts(Bruce)
47+
<NOT DONE YET> Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
48+
Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
49+
CURRENT_USER(Thomas)
50+
Speedup by inlining some frequently-called functions
51+
Modify constraint syntax to be SQL92-compliant(Thomas)
52+
Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas)
53+
Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
54+
Allow NOT NULL UNIQUE constraint clause (each allowed separately before)(Thomas)
55+
Allow Postgres-style casting ("::") of non-constants(Thomas)
56+
Add support for SQL3 TRUE and FALSE boolean constants(Thomas)
57+
Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE(Thomas)
58+
Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas)
59+
Allow SQL92 delimited identifiers(Thomas)
60+
Implement SQL92 binary and hexadecimal string decoding (b'10' and x'1F')(Thomas)
61+
Support SQL92 syntax for type coercion of literal strings
62+
(e.g. "DATETIME 'now'")(Thomas)
63+
Add conversions for int2, int4, and OID types to and from text(Thomas)
64+
Use shared lock when building indices(Vadim)
65+
Free memory allocated for an user query inside transaction block after
66+
this query is done, was turned off in <= 6.2.1(Vadim)
67+
New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)
68+
New PostgreSQL Procedural Language (PL) backend interface(Jan)
69+
Rename pg_dump -H option to -h(Bruce)
70+
Add Java support for passwords, European dates(Peter)
71+
Use indices for LIKE and ~, !~ operations(Bruce)
72+
Add hash functions for datetime and timespan(Thomas)
73+
Time Travel removed(Vadim, Bruce)
74+
Add paging for \d and \z, and fix \i(Bruce)
75+
Add Unix domain socket support to backend and to frontend library(Goran)
76+
Implement CREATE DATABASE/WITH LOCATION and initlocation utility(Thomas)
77+
Allow more SQL92 and/or Postgres reserved words as column identifiers(Thomas)
78+
Augment support for SQL92 SET TIME ZONE...(Thomas)
79+
SET/SHOW/RESET TIME ZONE uses TZ backend environment variable(Thomas)
80+
Implement SET keyword = DEFAULT and SET TIME ZONE DEFAULT(Thomas)
81+
Enable SET TIME ZONE using TZ environment variable(Thomas)
82+
Add PGDATESTYLE environment variable to frontend and backend initialization(Thomas)
83+
Add PGTZ, PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO
84+
frontend library initialization environment variables(Thomas)
85+
Regression tests time zone automatically set with "setenv PGTZ PST8PDT"(Thomas)
86+
Add pg_description table for info on tables, columns, operators, types, and
87+
aggregates(Bruce)
88+
Increase 16 char limit on system table/index names to 32 characters(Bruce)
89+
Rename system indices(Bruce)
90+
Add 'GERMAN' option to SET DATESTYLE(Thomas)
91+
Define an "ISO-style" timespan output format with "hh:mm:ss" fields(Thomas)
92+
Allow fractional values for delta times (e.g. '2.5 days')(Thomas)
93+
Validate numeric input more carefully for delta times(Thomas)
94+
Implement day of year as possible input to date_part()(Thomas)
95+
Define timespan_finite() and text_timespan() functions(Thomas)
96+
Remove archive stuff(Bruce)
97+
Allow for a pg_password authentication database that is separate from
98+
the system password file(Todd)
99+
Dump ACLs, GRANT, REVOKE permissions(Matt)
100+
Define text, varchar, and bpchar string length functions(Thomas)
101+
Fix Query handling for inheritance, and cost computations(Bruce)
102+
Implement CREATE TABLE/AS SELECT (alternative to SELECT/INTO)(Thomas)
103+
Allow NOT, IS NULL, IS NOT NULL in constraints(Thomas)
104+
Implement UNIONs for SELECT(Bruce)
105+
Add UNION, GROUP, DISTINCT to INSERT(Bruce)
106+
varchar() stores only necessary bytes on disk(Bruce)
107+
Fix for BLOBs(Peter)
108+
Mega-Patch for JDBC...see README_6.3 for list of changes(Peter)
109+
Allow installation data block size and max tuple size configuration(Darren)
110+
Remove unused "option" from PQconnectdb()
111+
New LOCK command and lock manual page describing deadlocks(Bruce)
112+
Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
113+
Enhance psql \z to show sequences(Bruce)
114+
Show NOT NULL and DEFAULT in psql \d table(Bruce)
115+
New psql .psqlrc file startup(Andrew)
116+
Modify sample startup script in contrib/linux to show syslog(Thomas)
117+
New types for IP and MAC addresses in contrib/ip_and_mac(TomH)
118+
Unix system time conversions with date/time types in contrib/unixdate(Thomas)
119+
Update of contrib stuff(Massimo)
120+
Add Unix socket support to DBD::Pg(Goran)
121+
New python interface (PyGreSQL 2.0)(D'Arcy)
122+
New frontend/backend protocol has a version number, network byte order(Phil)
123+
Security features in pg_hba.conf enhanced and documented, many cleanups(Phil)
124+
New HTML and Postscript documentation(Thomas)
125+
126+
127+
Source Tree Changes
128+
-------------------
129+
Add new html development tools, and flow chart in /tools/backend
130+
Fix for SCO compiles
131+
Stratus computer port "Gillies, Robert" <GilliesR@Nichols.com>
132+
Added support for shlib for BSD44_derived & i386_solaris
133+
Make configure more automated(Brook)
134+
Add script to check regression test results
135+
Break parser functions into smaller files, group together(Bruce)
136+
Rename heap_create to heap_create_and_catalog, rename heap_creatr
137+
to heap_create()(Bruce)
138+
Sparc/Linux patch for locking(TomS)
139+
Remove PORTNAME and reorganize port-specific stuff(Marc)
140+
Add optimizer README file(Bruce)
141+
Remove some recursion in optimizer and clean up some code there(Bruce)
142+
Fix for NetBSD locking(Henry)
143+
Fix for libptcl make(Tatsuo)
144+
AIX patch(Darren)
145+
Change IS TRUE, IS FALSE, ... to expressions using "=" rather than
146+
function calls to istrue() or isfalse() to allow optimization(Thomas)
147+
Various fixes NetBSD/Sparc related(TomH)
148+
Alpha linux locking(Travis,Ryan)
149+
Change elog(WARN) to elog(ERROR)(Bruce)
150+
FAQ for FreeBSD(Marc)
151+
Bring in the PostODBC source tree as part of our standard distribution(Marc)
152+
A minor patch for HP/UX 10 vs 9(Stan)
153+
New pg_attribute.atttypmod for type-specific info like varchar length(Bruce)
154+
Unixware patches(Billy)
155+
New i386 'lock' for spin lock asm(Billy)
156+
Support for multiplexed backends is removed
157+
Start an OpenBSD port
158+
Start an AUX port
159+
Start a Cygnus port
160+
Add string functions to regression suite(Thomas)
161+
Expand a few function names formerly truncated to 16 characters(Thomas)
162+
163+
1164
PostgreSQL 6.2.1 Fri Oct 17 00:01:27 EDT 1997
2165
-------------------------------------------------------------
3166

‎INSTALL

Lines changed: 14 additions & 14 deletions
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.2.1. Up to date information on PostgreSQL may be found at
5+
PostgreSQL v6.3. 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
@@ -110,7 +110,7 @@ PostgreSQL:
110110

111111
To check for disk space, use command "df -k".
112112

113-
4) Ftp file ftp://ftp.postgresql.org/pub/postgresql-v6.2.1.tar.gz from the
113+
4) Ftp file ftp://ftp.postgresql.org/pub/postgresql-v6.3.tar.gz from the
114114
Internet. Store it in your home directory.
115115

116116
5) Some platforms use flex. If your system uses flex then make sure
@@ -149,11 +149,10 @@ PostgreSQL:
149149
to change often every few weeks with no notice besides a quick comment
150150
in the HACKERS mailing list. Full releases always require a dump/reload
151151
from previous releases. It is therefore a bad idea to skip this
152-
step. Also, do not use the pg_dumpall script from v6.0 or everything
153-
will be owned by the Postgres super user. Type (with the gunzip line
154-
and the following line typed as one line):
152+
step. Type (with the gunzip line and the following line typed as one
153+
line):
155154
cd
156-
gunzip -c postgresql-v6.2.1.tar.gz |
155+
gunzip -c postgresql-v6.3.tar.gz |
157156
tar xvf - src/bin/pg_dump/pg_dumpall
158157
chmod a+x src/bin/pg_dump/pg_dumpall
159158
src/bin/pg_dump/pg_dumpall > db.out
@@ -218,7 +217,7 @@ PostgreSQL:
218217

219218
10) Unzip and untar the new source file. Type
220219
cd /usr/src/pgsql
221-
gunzip -c ~/postgresql-v6.2.1.tar.gz | tar xvf -
220+
gunzip -c ~/postgresql-v6.3.tar.gz | tar xvf -
222221

223222
11) Configure the source code for your system. It is this step at which
224223
you can specify your actual source path and installation paths for
@@ -358,9 +357,10 @@ PostgreSQL:
358357
location of this file will change accordingly.) This file should be
359358
made read only again once you are finsihed.
360359

361-
If you are upgrading from v6.0 you can copy file pg_hba.conf from
362-
your old database on top of the one in your new database, rather than
363-
redoing this from scratch.
360+
If you are upgrading, you can NOT copy file pg_hba.conf from your
361+
old database on top of the one in your new database. You will
362+
have to re-do your changes.
363+
364364

365365
18) If you wish to skip the regression tests then skip to step 21.
366366
However, we think skipping the tests is a BAD idea!
@@ -405,7 +405,7 @@ PostgreSQL:
405405
PostgreSQL.
406406

407407
For a i686/Linux-ELF platform, no tests failed since this is the
408-
v6.2.1 regression testing reference platform.
408+
v6.3 regression testing reference platform.
409409

410410
For the SPARC/Linux-ELF platform, using the 970525 beta version of
411411
PostgreSQL v6.2 the following tests "failed":
@@ -417,7 +417,7 @@ PostgreSQL:
417417
the differences and then decide if those differences will affect your
418418
intended use of PostgreSQL. However, keep in mind that this is likely
419419
to be the most solid release of PostgreSQL to date, incorporating many
420-
bug fixes from v6.1, and that previous versions of PostgreSQL have been
420+
bug fixes from v6.2.1, and that previous versions of PostgreSQL have been
421421
in use successfully for some time now.
422422

423423
After running the tests, type
@@ -525,7 +525,7 @@ PostgreSQL:
525525
rm -rf /usr/local/pgsql_6_0
526526
# Also delete old database directory tree if it is not in
527527
# /usr/local/pgsql_6_0/data
528-
rm ~/postgresql-v6.2.1.tar.gz
528+
rm ~/postgresql-v6.3.tar.gz
529529

530530
26) You will probably want to print out the documentation. Here is how
531531
you might do it if you have Ghostscript on your system and are
@@ -552,7 +552,7 @@ PostgreSQL:
552552
supported platforms. We therefore ask you to let us know if you did
553553
or did not get PostgreSQL to work on you system. Please send a
554554
mail message to pgsql-ports@postgresql.org telling us the following:
555-
- The version of PostgreSQL (v6.2.1, 6.1.1, beta 970703, etc.).
555+
- The version of PostgreSQL (v6.3, 6.2.1, beta 970703, etc.).
556556
- Your operating system (i.e. RedHat v4.0 Linux v2.0.26).
557557
- Your hardware (SPARC, i486, etc.).
558558
- Did you compile, install and run the regression tests cleanly?

‎README

Lines changed: 1 addition & 1 deletion
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.2.1 release of the PostgreSQL
5+
This directory contains the version 6.3 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

Lines changed: 69 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Wed Oct 15 23:16:48 EDT 1997
5-
Version: 6.2.1
4+
Last updated: Sun Feb 1 16:13:28 EST 1998
65

76
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
87

@@ -14,8 +13,6 @@
1413

1514
Irix-specific questions are answered in
1615
http://postgreSQL.org/docs/FAQ-irix.shtml.
17-
18-
Changes in this version (* = modified, + = new):
1916
_________________________________________________________________
2017

2118
Questions answered:
@@ -29,14 +26,15 @@ Questions answered:
2926
1.5) Support for PostgreSQL
3027
1.6) Latest release of PostgreSQL
3128
1.7) Is there a commercial version of PostgreSQL?
32-
1.8) What version of SQL does PostgreSQL use?
33-
1.9) What documentation is available for PostgreSQL?
29+
1.8) What documentation is available for PostgreSQL?
30+
1.9) What version of SQL does PostgreSQL use?
3431
1.10) Does PostgreSQL work with databases from earlier versions of
3532
postgres?
3633
1.11) Are there ODBC drivers for PostgreSQL?
3734
1.12) What tools are available for hooking postgres to Web pages?
3835
1.13) Does PostgreSQL have a graphical user interface? A report
3936
generator? A embedded query language interface?
37+
1.14) What is a good book to learn SQL?
4038

4139
2) Installation/Configuration questions
4240

@@ -91,6 +89,9 @@ Questions answered:
9189
3.22) What is Genetic Query Optimization?
9290
3.23) How do you remove a column from a table?
9391
3.24) How do SELECT only the first few rows of a query?
92+
3.25) Why can't I create a column named "time"?
93+
3.26) How much database disk space is required to store data from a
94+
typical flat file?
9495

9596
4) Questions about extending PostgreSQL
9697

@@ -242,8 +243,10 @@ Section 1: General Questions
242243
1.6) Latest release of PostgreSQL
243244

244245
The latest release of PostgreSQL is version 6.2.1, which was released
245-
on October 17th, 1997. For information about what is new in 6.2.1, see
246-
our TODO list on our WWW page.
246+
on October 17th, 1997. We are testing 6.3 beta. For information about
247+
what is new in 6.3, see our TODO list on our WWW page.
248+
249+
We plan to have major releases every three months.
247250

248251
1.7) Is there a commercial version of PostgreSQL?
249252

@@ -279,14 +282,16 @@ Section 1: General Questions
279282

280283
PostgreSQL v1.09 is compatible with databases created with v1.01.
281284

285+
Upgrading to 6.3 from earlier releases requires a dump and restore.
286+
282287
Upgrading to 6.2.1 from pre-6.2 requires a dump and restore.
283288

284289
Upgrading to 6.2.1 from 6.2 does not require a dump, but see the
285290
appropriate /migration file in the distribution.
286291

287292
Those ugrading from versions earlier than 1.09 must upgrade to 1.09
288293
first without a dump/reload, then dump the data from 1.09, and then
289-
load it into 6.2.1.
294+
load it into 6.2.1 or 6.3 beta.
290295

291296
1.11) Are there ODBC drivers for PostgreSQL?
292297

@@ -312,15 +317,15 @@ Section 1: General Questions
312317

313318
1.12) What tools are available for hooking postgres to Web pages?
314319

315-
For web integration, PHP/FI is an excellent interface. The URL for
316-
that is http://www.vex.net/php/
320+
A nice introduction to Database-backed Web pages can be seen at:
321+
http://www.webtools.com
322+
323+
For web integration, PHP is an excellent interface. The URL for that
324+
is http://php.iquest.net
317325

318326
PHP is great for simple stuff, but for more complex stuff, some still
319327
use the perl interface and CGI.pm.
320328

321-
An example of using WWW with C to talk to Postgres is can be tried at:
322-
* http://postgreSQL.org/~mlc
323-
324329
An WWW gatway based on WDB using perl can be downloaded from:
325330
* http://www.eol.ists.ca/~dunlop/wdb -p95
326331

@@ -331,6 +336,11 @@ Section 1: General Questions
331336
reported some success at using 'pgbrowse' and 'onyx' as frontends to
332337
PostgreSQL. Several contributions are working on tk based frontend
333338
tools. Ask on the mailing list.
339+
340+
1.14) What is a good book to learn SQL?
341+
342+
Many of our users like The Practical SQL Handbook, Bowman et al,
343+
Addison Wesley.
334344
_________________________________________________________________
335345

336346
Section 2: Installation Questions
@@ -409,9 +419,9 @@ Section 2: Installation Questions
409419
this parameter too high, the process will not start or crash
410420
unexpectedly. Each buffer is 8K and the defualt is 64 buffers.
411421

412-
You can also use the postmaster -S option to increase the maximum
413-
amount of memory used by each backend process for temporary sorts.
414-
Each buffer is 1K and the defualt is 512 buffers.
422+
You can also use the postgres -S option to increase the maximum amount
423+
of memory used by each backend process for temporary sorts. Each
424+
buffer is 1K and the defualt is 512 buffers.
415425

416426
2.12) What debugging features are available in PostgreSQL?
417427

@@ -600,10 +610,10 @@ BYTEA bytea variable-length array of bytes
600610
these fields or when doing other internal operations.
601611

602612
The last four types above are "varlena" types (i.e. the first four
603-
bytes is the length, followed by the data). CHAR(#) and VARCHAR(#)
604-
allocate the maximum number of bytes no matter how much data is stored
605-
in the field. TEXT and BYTEA are the only character types that have
606-
variable length on the disk.
613+
bytes are the length, followed by the data). CHAR(#) allocates the
614+
maximum number of bytes no matter how much data is stored in the
615+
field. TEXT, VARCHAR(#), and BYTEA all have variable length on the
616+
disk.
607617

608618
3.13) In a query, how do I detect if a field is NULL?
609619

@@ -708,7 +718,7 @@ BYTEA bytea variable-length array of bytes
708718
separate tables. These oids can be used to identify specific user rows
709719
and used in joins. It is recommended you use column type oid to store
710720
oid values. See the sql(l) manual page to see the other internal
711-
columns.
721+
columns. You can create an index on the oid field for faster access.
712722

713723
Tids are used to indentify specific physical rows with block and
714724
offset values. Tids change after rows are modified or reloaded. They
@@ -750,14 +760,49 @@ BYTEA bytea variable-length array of bytes
750760
DROP TABLE old_table;
751761
ALTER TABLE new_table RENAME TO old_table;
752762

753-
3.23) How do SELECT only the first few rows of a query?
763+
3.24) How do SELECT only the first few rows of a query?
754764

755765
See the fetch manual page.
756766

757767
This only prevents all row results from being transfered to the
758768
client. The entire query must be evaluated, even if you only want just
759769
first few rows. Consider a query that has and ORDER BY. There is no
760770
way to return any rows until the entire query is evaluated and sorted.
771+
772+
3.25) Why can't I create a column named "time"?
773+
774+
6.2.1 has added some new restricted keywords as we make PostgreSQL
775+
more ANSI-92 compilant. The next release will have this restriction
776+
removed. There is a patch on ftp.postgresql.org that will allow this
777+
feature now.
778+
779+
3.26)How much database disk space is required to store data from a typical
780+
flat file?
781+
782+
Consider a file with 300,000 lines with two integers on each line. The
783+
flat file is 2.4MB. The size of the PostgreSQL database file
784+
containing this data can be estimated:
785+
786+
40 bytes + each row header (approximate)
787+
8 bytes + two int fields @ 4 bytes each
788+
4 bytes + pointer on page to tuple
789+
-------- =
790+
52 bytes per row
791+
792+
The data page size in PostgreSQL is 8192(8k) bytes, so:
793+
794+
8192 bytes per page
795+
------------------- = 157 rows per database page (rounded up)
796+
52 bytes per row
797+
798+
300000 data rows
799+
----------------- = 1911 database pages
800+
157 rows per page
801+
802+
1911 database pages * 8192 bytes per page = 15,654,912 or 15.5MB
803+
804+
Indexes do not contain as much overhead, but do contain the data that
805+
is being indexed, so they can be large also.
761806
_________________________________________________________________
762807

763808
Section 4: Extending PostgreSQL
@@ -803,4 +848,4 @@ Section 5: Bugs
803848
You can also fill out the "bug-template" file and send it to:
804849
* bugs@postgreSQL.org
805850

806-
This is the address of the developers mailing list.
851+
This is the address of the developers mailing list.

‎doc/TODO

Lines changed: 245 additions & 177 deletions
Large diffs are not rendered by default.

‎doc/bug.template

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ System Configuration
2727

2828
Operating System (example: Linux 2.0.26 ELF) :
2929

30-
PostgreSQL version (example: PostgreSQL-6.2.1): PostgreSQL-6.2.1
30+
PostgreSQL version (example: PostgreSQL-6.3) : PostgreSQL-6.3
3131

3232
Compiler used (example: gcc 2.7.2) :
3333

‎register.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11

22

3-
(1997-10-01)
3+
(1998-02-01)
44
PostgreSQL has a Web site at http://www.postgresql.org/ which carries details
55
on the latest release, upcoming features, and other information to make your
66
work or play with PostgreSQL more productive.

0 commit comments

Comments
 (0)
Please sign in to comment.