Update stuff for 6.5.1 release.

This commit is contained in:
Bruce Momjian 1999-07-10 16:28:02 +00:00
parent 4fceee0e71
commit 5a3fa95c39
9 changed files with 551 additions and 485 deletions

2
README
View File

@ -2,7 +2,7 @@
PostgreSQL Data Base Management System (formerly known as Postgres, then
as Postgres95).
This directory contains the development version of 6.5 of the PostgreSQL
This directory contains the development version of 6.5.1 of the PostgreSQL
database server. The server is not ANSI SQL compliant, but it gets
closer with every release. After you unzip and untar the distribution
file, look at file INSTALL for the installation notes and file HISTORY

946
doc/FAQ

File diff suppressed because it is too large Load Diff

View File

@ -1,12 +1,12 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Mon Feb 22 17:15:06 EST 1999
Last updated: Sat Jul 10 00:38:09 EDT 1999
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.
postgreSQL Web site, http://PostgreSQL.org.
_________________________________________________________________
Questions
@ -24,6 +24,8 @@
9) How do I efficiently access information in tables from the backend
code?
10) What is elog()?
11) What is configure all about?
12) How do I add a new port?
_________________________________________________________________
1) What tools are available for developers?
@ -294,7 +296,7 @@ s
While scans automatically lock/unlock rows from the buffer cache, with
heap_fetch(), you must pass a Buffer pointer, and ReleaseBuffer() it
when completed. Once you have the row, you can get data that is common
to all tuples, like t_self and t_oid, by mererly accessing the
to all tuples, like t_self and t_oid, by merely accessing the
HeapTuple structure entries. If you need a table-specific column, you
should take the HeapTuple pointer, and use the GETSTRUCT() macro to
access the table-specific start of the tuple. You then cast the
@ -324,3 +326,41 @@ s
current query, never returning from the call. FATAL terminates the
backend process. The remaining parameters of elog are a printf-style
set of parameters to print.
11) What is configure all about?
The files configure and configure.in are part of the GNU autoconf
package. Configure allows us to test for various capabilities of the
OS, and to set variables that can then be tested in C programs and
Makefiles. Autoconf is installed on the PostgreSQL main server. To add
options to configure, edit configure.in, and then run autoconf to
generate configure.
When configure is run by the user, it tests various OS capabilities,
stores those in config.status and config.cache, and modifies a list of
*.in files. For example, if there exists a Makefile.in, configure
generates a Makefile that contains substitutions for all @var@
parameters found by configure.
When you need to edit files, make sure you don't waste time modifying
files generated by configure. Edit the *.in file, and re-run configure
to recreate the needed file. If you run make distclean from the
top-level source directory, all files derived by configure are
removed, so you see only the file contained in the source
distribution.
12) How do I add a new port?
There are a variety of places that need to be modified to add a new
port. First, start in the src/template directory. Add an appropriate
entry for your OS. Also, use src/config.guess to add your OS to
src/template/.similar. You shouldn't match the OS version exactly. The
configure test will look for an exact OS version number, and if not
found, find a match without version number. Edit src/configure.in to
add your new OS. (See configure item above.) You will need to run
autoconf, or patch src/configure too.
Then, check src/include/port and add your new OS file, with
appropriate values. Hopefully, there is already locking code in
src/include/storage/s_lock.h for your CPU. There is a backend/port
directory if you need special files for your OS.

View File

@ -27,7 +27,7 @@ System Configuration
Operating System (example: Linux 2.0.26 ELF) :
PostgreSQL version (example: PostgreSQL-6.5) : PostgreSQL-6.5
PostgreSQL version (example: PostgreSQL-6.5.1): PostgreSQL-6.5.1
Compiler used (example: gcc 2.8.0) :

View File

@ -4,7 +4,7 @@
<Abstract>
<Para>
Complete installation instructions for
<ProductName>Postgres</ProductName> v6.5.
<ProductName>Postgres</ProductName> v6.5.1.
</Para>
</Abstract>
@ -170,8 +170,8 @@ remaining steps in the installation will happen in this account.
<Step Performance="required">
<Para>
Ftp file
<ulink url="ftp://ftp.postgresql.org/pub/postgresql-v6.5.tar.gz">
<filename>ftp://ftp.postgresql.org/pub/postgresql-v6.5.tar.gz</filename></ulink>
<ulink url="ftp://ftp.postgresql.org/pub/postgresql-v6.5.1.tar.gz">
<filename>ftp://ftp.postgresql.org/pub/postgresql-v6.5.1.tar.gz</filename></ulink>
from the Internet. Store it in your home directory.
</Para>
</Step>
@ -241,7 +241,11 @@ $ rm -rf flex-2.5.4
<Para>
If you are not upgrading an existing system then skip to
<xref linkend="newdirs">.
If you are upgrading an existing system then back up your database.
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
@ -271,7 +275,7 @@ from the new distribution:
<ProgramListing>
$ cd
$ gunzip -c postgresql-v6.5.tar.gz \
$ 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
@ -414,7 +418,7 @@ $ exit
Unzip and untar the new source file. Type
<ProgramListing>
$ cd /usr/src/pgsql
$ gunzip -c ~/postgresql-v6.5.tar.gz | tar xvf -
$ gunzip -c ~/postgresql-v6.5.1.tar.gz | tar xvf -
</ProgramListing>
</Para>
</Step>
@ -997,7 +1001,7 @@ For example,
<listitem>
<Para>
For a i686/Linux-ELF platform, no tests failed since this is the
v6.5 regression testing reference platform.
v6.5.1 regression testing reference platform.
</Para>
</listitem>
@ -1111,7 +1115,7 @@ $ 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.tar.gz
$ rm ~/postgresql-v6.5.1.tar.gz
</ProgramListing>
</Para>
</Step>
@ -1158,7 +1162,7 @@ $ lpr -l -s -r manpage.hp
<itemizedlist>
<listitem>
<para>
The version of <ProductName>Postgres</ProductName> (v6.5, 6.4.2, beta 981014, etc.).
The version of <ProductName>Postgres</ProductName> (v6.5.1, 6.5, beta 990318, etc.).
</para>
</listitem>

View File

@ -1,6 +1,6 @@
(1999-06-09)
(1999-07-15)
PostgreSQL has a Web site at http://www.postgresql.org/ which carries details
on the latest release, upcoming features, and other information to make your
work or play with PostgreSQL more productive.

View File

@ -4,7 +4,7 @@
* this file contains the interface to version.c.
* Also some parameters.
*
* $Header: /cvsroot/pgsql/src/include/Attic/version.h.in,v 1.5 1999/02/14 04:56:54 momjian Exp $
* $Header: /cvsroot/pgsql/src/include/Attic/version.h.in,v 1.6 1999/07/10 16:28:01 momjian Exp $
*
*-------------------------------------------------------------------------
*/
@ -16,7 +16,7 @@ void SetPgVersion(const char *path, char **reason_p);
#define PG_RELEASE "6"
#define PG_VERSION "5"
#define PG_SUBVERSION "0"
#define PG_SUBVERSION "1"
#define PG_VERFILE "PG_VERSION"

View File

@ -1,8 +1,8 @@
#include <winver.h>
VS_VERSION_INFO VERSIONINFO
FILEVERSION 6,5,0,0
PRODUCTVERSION 6,5,0,0
FILEVERSION 6,5,1,0
PRODUCTVERSION 6,5,1,0
FILEFLAGSMASK 0x3fL
FILEFLAGS 0
FILEOS VOS__WINDOWS32
@ -15,13 +15,13 @@ BEGIN
BEGIN
VALUE "CompanyName", "\0"
VALUE "FileDescription", "PostgreSQL Access Library\0"
VALUE "FileVersion", "6, 5, 0, 0\0"
VALUE "FileVersion", "6, 5, 1, 0\0"
VALUE "InternalName", "libpq\0"
VALUE "LegalCopyright", "Copyright (C) 1999\0"
VALUE "LegalTrademarks", "\0"
VALUE "OriginalFilename", "libpq.dll\0"
VALUE "ProductName", "PostgreSQL\0"
VALUE "ProductVersion", "6, 5, 0, 0\0"
VALUE "ProductVersion", "6, 5, 1, 0\0"
END
END
BLOCK "VarFileInfo"

View File

@ -1,15 +1,13 @@
README
INSTALL
HISTORY
register.txt
doc/Machine-specific FAQ's
doc/TODO
doc/bug.template
update include/version.h.in after release, including subversion
update backend/parser/scan.c and gram.c so flex/bison not necessary
update pgaccess
update odbc
update doc/src/sgml/release.sgml
update doc/src/sgml/install.sgml
update interfaces/libpq/libpq.rc
update documentation
command-line arg printout from inside the program