Index: doc/src/sgml/admin.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/admin.sgml,v
retrieving revision 1.40
diff -c -r1.40 admin.sgml
*** doc/src/sgml/admin.sgml 24 Oct 2002 17:48:54 -0000 1.40
--- doc/src/sgml/admin.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 25,37 ****
What's In This Book
! This book covers topics that are of interest to a PostgreSQL
! database administrator. This includes installation of the
! software, set up and configuration of the server, management of
! users and databases, and maintenance tasks. Anyone who runs a
! PostgreSQL server, either for personal use, but especially in
! production, should be familiar with the topics covered in this
! book.
--- 25,37 ----
What's In This Book
! This book covers topics that are of interest to a
! PostgreSQL database administrator. This includes
! installation of the software, set up and configuration of the
! server, management of users and databases, and maintenance tasks.
! Anyone who runs a PostgreSQL server, either for
! personal use, but especially in production, should be familiar
! with the topics covered in this book.
***************
*** 49,57 ****
up their own server can begin their exploration with this book.
The rest of this book which is about tuning and management
presupposes that the reader is familiar with the general use of
! the PostgreSQL database system. Readers are encouraged to look at
! the &cite-tutorial; and the &cite-user; for additional
! information.
--- 49,57 ----
up their own server can begin their exploration with this book.
The rest of this book which is about tuning and management
presupposes that the reader is familiar with the general use of
! the PostgreSQL database system. Readers are
! encouraged to look at the &cite-tutorial; and the &cite-user; for
! additional information.
Index: doc/src/sgml/charset.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/charset.sgml,v
retrieving revision 2.29
diff -c -r2.29 charset.sgml
*** doc/src/sgml/charset.sgml 21 Sep 2002 18:32:52 -0000 2.29
--- doc/src/sgml/charset.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 351,357 ****
! Multibyte support is enabled by default since PostgreSQL version 7.3.
--- 351,358 ----
! Multibyte support is enabled by default since
! PostgreSQL version 7.3.
***************
*** 574,580 ****
encoding conversion between server and client for some
encodings. The conversion info is stored in pg_conversion system
catalog. You can create a new conversion by using CREATE
! CONVERSION. PostgreSQL comes with some predefined
conversions. They are listed in .
--- 575,581 ----
encoding conversion between server and client for some
encodings. The conversion info is stored in pg_conversion system
catalog. You can create a new conversion by using CREATE
! CONVERSION. PostgreSQL comes with some predefined
conversions. They are listed in .
Index: doc/src/sgml/client-auth.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/client-auth.sgml,v
retrieving revision 1.40
diff -c -r1.40 client-auth.sgml
*** doc/src/sgml/client-auth.sgml 11 Nov 2002 20:14:02 -0000 1.40
--- doc/src/sgml/client-auth.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 160,168 ****
user
! Specifies which PostgreSQL users this record matches. The value
! all specifies that it matches all users.
! Otherwise, this is the name of a specific
PostgreSQL user. Multiple user names
can be supplied by separating them with commas. Group names can
be specified by preceding the group name with +. A
--- 160,168 ----
user
! Specifies which PostgreSQL users this record
! matches. The value all specifies that it
! matches all users. Otherwise, this is the name of a specific
PostgreSQL user. Multiple user names
can be supplied by separating them with commas. Group names can
be specified by preceding the group name with +. A
Index: doc/src/sgml/datatype.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/datatype.sgml,v
retrieving revision 1.107
diff -c -r1.107 datatype.sgml
*** doc/src/sgml/datatype.sgml 11 Nov 2002 20:14:02 -0000 1.107
--- doc/src/sgml/datatype.sgml 14 Nov 2002 00:58:52 -0000
***************
*** 245,258 ****
Compatibility
! The following types (or spellings thereof) are specified by SQL:
! bit, bit varying, boolean,
! char, character, character
! varying, varchar, date,
! double precision, integer,
! interval, numeric, decimal,
! real, smallint, time,
! timestamp (both with or without time zone).
--- 245,259 ----
Compatibility
! The following types (or spellings thereof) are specified by
! SQL: bit, bit
! varying, boolean, char,
! character, character varying,
! varchar, date, double
! precision, integer, interval,
! numeric, decimal, real,
! smallint, time, timestamp
! (both with or without time zone).
***************
*** 464,474 ****
! SQL only specifies the integer types integer (or
! int) and smallint. The type
! bigint, and the type names int2,
! int4, and int8 are extensions, which
! are shared with various other SQL database systems.
--- 465,476 ----
! SQL only specifies the integer types
! integer (or int) and
! smallint. The type bigint, and the
! type names int2, int4, and
! int8 are extensions, which are shared with various
! other SQL database systems.
***************
*** 536,548 ****
NUMERIC
without any precision or scale creates a column in which numeric
! values of any precision and scale can be stored, up to the implementation
! limit on precision. A column of this kind will not coerce input
! values to any particular scale, whereas numeric columns
! with a declared scale will coerce input values to that scale.
! (The SQL standard requires a default scale of 0, i.e., coercion to
! integer precision. We find this a bit useless. If you're concerned about
! portability, always specify the precision and scale explicitly.)
--- 538,552 ----
NUMERIC
without any precision or scale creates a column in which numeric
! values of any precision and scale can be stored, up to the
! implementation limit on precision. A column of this kind will
! not coerce input values to any particular scale, whereas
! numeric columns with a declared scale will coerce
! input values to that scale. (The SQL standard
! requires a default scale of 0, i.e., coercion to integer
! precision. We find this a bit useless. If you're concerned
! about portability, always specify the precision and scale
! explicitly.)
***************
*** 554,560 ****
The types decimal and numeric are
! equivalent. Both types are part of the SQL standard.
--- 558,565 ----
The types decimal and numeric are
! equivalent. Both types are part of the SQL
! standard.
***************
*** 806,812 ****
shows the
! general-purpose character types available in PostgreSQL.
--- 811,818 ----
shows the
! general-purpose character types available in
! PostgreSQL.
***************
*** 818,828 ****
longer string into a column of these types will result in an
error, unless the excess characters are all spaces, in which case
the string will be truncated to the maximum length. (This
! somewhat bizarre exception is required by the SQL standard.) If
! the string to be stored is shorter than the declared length,
! values of type character will be space-padded; values
! of type character varying will simply store the
! shorter string.
--- 824,835 ----
longer string into a column of these types will result in an
error, unless the excess characters are all spaces, in which case
the string will be truncated to the maximum length. (This
! somewhat bizarre exception is required by the
! SQL standard.) If the string to be stored is
! shorter than the declared length, values of type
! character will be space-padded; values of type
! character varying will simply store the shorter
! string.
***************
*** 831,837 ****
character(n) or character
varying(n), then an overlength value will
be truncated to n characters without raising an
! error. (This too is required by the SQL standard.)
--- 838,845 ----
character(n) or character
varying(n), then an overlength value will
be truncated to n characters without raising an
! error. (This too is required by the SQL
! standard.)
***************
*** 859,866 ****
more general text type, which stores strings of any
length. Unlike character varying, text
does not require an explicit declared upper limit on the size of
! the string. Although the type text is not in the SQL
! standard, many other RDBMS packages have it as well.
--- 867,875 ----
more general text type, which stores strings of any
length. Unlike character varying, text
does not require an explicit declared upper limit on the size of
! the string. Although the type text is not in the
! SQL standard, many other RDBMS packages have it
! as well.
***************
*** 1125,1136 ****
To use the bytea escaped octet notation, string
! literals (input strings) must contain two backslashes due because
! they must pass through two parsers in the PostgreSQL server. The
! first backslash is interpreted as an escape character by the
! string-literal parser, and therefore is consumed, leaving the
! characters that follow. The remaining backslash is recognized by
! the bytea input function as the prefix of a three
digit octal value. For example, a string literal passed to the
backend as '\\001' becomes
'\001' after passing through the string-literal
--- 1134,1145 ----
To use the bytea escaped octet notation, string
! literals (input strings) must contain two backslashes because they
! must pass through two parsers in the PostgreSQL
! server. The first backslash is interpreted as an escape character
! by the string-literal parser, and therefore is consumed, leaving
! the characters that follow. The remaining backslash is recognized
! by the bytea input function as the prefix of a three
digit octal value. For example, a string literal passed to the
backend as '\\001' becomes
'\001' after passing through the string-literal
***************
*** 1170,1190 ****
! Depending on the front end to PostgreSQL you use, you may have
! additional work to do in terms of escaping and unescaping
! bytea strings. For example, you may also have to escape
! line feeds and carriage returns if your interface automatically
! translates these. Or you may have to double up on backslashes if
! the parser for your language or choice also treats them as an
! escape character.
!
! The SQL standard defines a different binary string type, called
! BLOB or BINARY LARGE OBJECT. The input
! format is different compared to bytea, but the
! provided functions and operators are mostly the same.
!
--- 1179,1200 ----
! Depending on the front end to PostgreSQL you use,
! you may have additional work to do in terms of escaping and
! unescaping bytea strings. For example, you may also
! have to escape line feeds and carriage returns if your interface
! automatically translates these. Or you may have to double up on
! backslashes if the parser for your language or choice also treats
! them as an escape character.
!
! The SQL standard defines a different binary
! string type, called BLOB or BINARY LARGE
! OBJECT. The input format is different compared to
! bytea, but the provided functions and operators are
! mostly the same.
!
***************
*** 1781,1791 ****
Output formats can be set to one of the four styles ISO 8601,
SQL (Ingres), traditional PostgreSQL, and
German, using the SET DateStyle. The default
! is the ISO format. (The SQL standard requires
! the use of the ISO 8601 format. The name of the
! SQL output format is a historical accident.)
! shows examples of
! each output style. The output of the date and
time types is of course only the date or time part
in accordance with the given examples.
--- 1791,1802 ----
Output formats can be set to one of the four styles ISO 8601,
SQL (Ingres), traditional PostgreSQL, and
German, using the SET DateStyle. The default
! is the ISO format. (The
! SQL standard requires the use of the ISO 8601
! format. The name of the SQL output format is a
! historical accident.) shows examples of each
! output style. The output of the date and
time types is of course only the date or time part
in accordance with the given examples.
***************
*** 1920,1953 ****
! To address these difficulties, we recommend using date/time
! types that contain both date and time when using time zones. We
! recommend not using the type time
! with time zone (though it is supported by
PostgreSQL for legacy applications and
! for compatibility with other SQL implementations).
! PostgreSQL
! assumes your local time zone for any type containing only
! date or time. Further, time zone support is derived from
! the underlying operating system
! time-zone capabilities, and hence can handle daylight-saving time
! and other expected behavior.
! PostgreSQL obtains time-zone support
from the underlying operating system for dates between 1902 and
2038 (near the typical date limits for Unix-style
systems). Outside of this range, all dates are assumed to be
! specified and used in Universal Coordinated Time (UTC).
! All dates and times are stored internally in UTC,
! traditionally known as Greenwich Mean Time (GMT).
! Times are converted to local time on the database server before being
! sent to the client frontend, hence by default are in the server
! time zone.
--- 1931,1964 ----
! To address these difficulties, we recommend using date/time types
! that contain both date and time when using time zones. We
! recommend not using the type time with
! time zone (though it is supported by
PostgreSQL for legacy applications and
! for compatibility with other SQL
! implementations). PostgreSQL assumes
! your local time zone for any type containing only date or
! time. Further, time zone support is derived from the underlying
! operating system time-zone capabilities, and hence can handle
! daylight-saving time and other expected behavior.
! PostgreSQL obtains time-zone support
from the underlying operating system for dates between 1902 and
2038 (near the typical date limits for Unix-style
systems). Outside of this range, all dates are assumed to be
! specified and used in Universal Coordinated Time
! (UTC).
! All dates and times are stored internally in
! UTC, traditionally known as Greenwich Mean
! Time (GMT). Times are converted to local time
! on the database server before being sent to the client frontend,
! hence by default are in the server time zone.
***************
*** 1993,2000 ****
! If an invalid time zone is specified,
! the time zone becomes GMT (on most systems anyway).
--- 2004,2011 ----
! If an invalid time zone is specified, the time zone becomes
! UTC (on most systems anyway).
***************
*** 2124,2131 ****
Geometric data types represent two-dimensional spatial
objects. shows the geometric
! types available in PostgreSQL. The most fundamental type, the
! point, forms the basis for all of the other types.
--- 2135,2143 ----
Geometric data types represent two-dimensional spatial
objects. shows the geometric
! types available in PostgreSQL. The
! most fundamental type, the point, forms the basis for all of the
! other types.
***************
*** 2746,2754 ****
! Prior to PostgreSQL 7.2, BIT data was
! always silently truncated or zero-padded on the right, with or without an
! explicit cast. This was changed to comply with the SQL standard.
--- 2758,2767 ----
! Prior to PostgreSQL 7.2, BIT data
! was always silently truncated or zero-padded on the right, with
! or without an explicit cast. This was changed to comply with the
! SQL standard.
***************
*** 2978,2991 ****
! A third identifier type used by the system is cid, or command
! identifier. This is the data type of the system columns
! cmin and cmax.
! Command identifiers are also 32-bit quantities. This creates a hard
! limit of 232 (4 billion) SQL commands within a single
! transaction.
! In practice this limit is not a problem --- note that the limit is on
! number of SQL commands, not number of tuples processed.
--- 2991,3004 ----
! A third identifier type used by the system is cid, or
! command identifier. This is the data type of the system columns
! cmin and cmax. Command
! identifiers are also 32-bit quantities. This creates a hard limit
! of 232 (4 billion) SQL commands
! within a single transaction. In practice this limit is not a
! problem --- note that the limit is on number of
! SQL commands, not number of tuples processed.
***************
*** 3044,3052 ****
column data type, but it can be used to declare a function's
argument or result type. Each of the available pseudo-types is
useful in situations where a function's behavior does not
! correspond to simply taking or returning a value of a specific SQL
! data type. lists the
! existing pseudo-types.
--- 3057,3066 ----
column data type, but it can be used to declare a function's
argument or result type. Each of the available pseudo-types is
useful in situations where a function's behavior does not
! correspond to simply taking or returning a value of a specific
! SQL data type. lists the existing
! pseudo-types.
***************
*** 3126,3139 ****
! The internal pseudo-type is used to declare functions that are
! meant only to be called internally by the database system, and not by
! direct invocation in a SQL query. If a function has at least one
! internal-type argument then it cannot be called from SQL.
! To preserve the type safety of this restriction it is important to
! follow this coding rule: do not create any function that is declared
! to return internal unless it has at least one internal
! argument.
--- 3140,3154 ----
! The internal pseudo-type is used to declare functions
! that are meant only to be called internally by the database
! system, and not by direct invocation in a SQL
! query. If a function has at least one internal-type
! argument then it cannot be called from SQL. To
! preserve the type safety of this restriction it is important to
! follow this coding rule: do not create any function that is
! declared to return internal unless it has at least one
! internal argument.
Index: doc/src/sgml/ddl.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ddl.sgml,v
retrieving revision 1.9
diff -c -r1.9 ddl.sgml
*** doc/src/sgml/ddl.sgml 11 Nov 2002 20:14:02 -0000 1.9
--- doc/src/sgml/ddl.sgml 14 Nov 2002 00:59:41 -0000
***************
*** 1103,1111 ****
ALTER TABLE products ALTER COLUMN price DROP DEFAULT;
This is equivalent to setting the default to null, at least in
! PostgreSQL. As a consequence, it is not an error to drop a
! default where one hadn't been defined, because the default is
! implicitly the null value.
--- 1103,1111 ----
ALTER TABLE products ALTER COLUMN price DROP DEFAULT;
This is equivalent to setting the default to null, at least in
! PostgreSQL. As a consequence, it is not an error
! to drop a default where one hadn't been defined, because the
! default is implicitly the null value.
***************
*** 1609,1616 ****
standard. Therefore, many users consider qualified names to
really consist of
username.tablename.
! This is how PostgreSQL will effectively behave if you create a per-user
! schema for every user.
--- 1609,1616 ----
standard. Therefore, many users consider qualified names to
really consist of
username.tablename.
! This is how PostgreSQL will effectively
! behave if you create a per-user schema for every user.
Index: doc/src/sgml/diskusage.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/diskusage.sgml,v
retrieving revision 1.7
diff -c -r1.7 diskusage.sgml
*** doc/src/sgml/diskusage.sgml 11 Nov 2002 20:14:02 -0000 1.7
--- doc/src/sgml/diskusage.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 6,16 ****
Monitoring Disk Usage
! This chapter discusses how to monitor the disk usage of a PostgreSQL
! database system. In the current release, the database administrator
! does not have much control over the on-disk storage layout, so this
! chapter is mostly informative and can give you some ideas how to
! manage the disk usage with operating system tools.
--- 6,17 ----
Monitoring Disk Usage
! This chapter discusses how to monitor the disk usage of a
! PostgreSQL database system. In the current
! release, the database administrator does not have much control over
! the on-disk storage layout, so this chapter is mostly informative
! and can give you some ideas how to manage the disk usage with
! operating system tools.
Index: doc/src/sgml/ecpg.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ecpg.sgml,v
retrieving revision 1.39
diff -c -r1.39 ecpg.sgml
*** doc/src/sgml/ecpg.sgml 24 Oct 2002 17:48:54 -0000 1.39
--- doc/src/sgml/ecpg.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 38,63 ****
for handling SQL commands from C code. First, it
takes care of the tedious passing of information to and from
variables in your C program. Secondly, embedded
! SQL in C is defined in the SQL standard and supported by many other
! SQL databases. The PostgreSQL implementation is designed to match
! this standard as much as possible, and it is usually possible to
! port embedded SQL programs written for other
RDBMS to PostgreSQL
with relative ease.
! As indicated, programs written for the embedded SQL interface are
! normal C programs with special code inserted to perform
! database-related actions. This special code always has the form
EXEC SQL ...;
These statements syntactically take the place of a C statement.
Depending on the particular statement, they may appear in the
! global context or within a function. Embedded SQL statements
! follow the case-sensitivity rules of normal SQL code, and not those
! of C.
--- 38,66 ----
for handling SQL commands from C code. First, it
takes care of the tedious passing of information to and from
variables in your C program. Secondly, embedded
! SQL in C is defined in the
! SQL standard and supported by many other
! SQL databases. The PostgreSQL
! implementation is designed to match this standard as much as
! possible, and it is usually possible to port embedded
! SQL programs written for other
RDBMS to PostgreSQL
with relative ease.
! As indicated, programs written for the embedded
! SQL interface are normal C programs with special
! code inserted to perform database-related actions. This special
! code always has the form
EXEC SQL ...;
These statements syntactically take the place of a C statement.
Depending on the particular statement, they may appear in the
! global context or within a function. Embedded
! SQL statements follow the case-sensitivity rules
! of normal SQL code, and not those of C.
***************
*** 748,755 ****
The preprocessor program is called ecpg and is
! included in a normal PostgreSQL installation. Embedded SQL
! programs are typically named with an extension
.pgc. If you have a program file called
prog1.pgc, you can preprocess it by simply
calling
--- 751,758 ----
The preprocessor program is called ecpg and is
! included in a normal PostgreSQL installation.
! Embedded SQL programs are typically named with an extension
.pgc. If you have a program file called
prog1.pgc, you can preprocess it by simply
calling
***************
*** 768,777 ****
cc -c prog1.c
The generated C source files include headers files from the
! PostgreSQL installation, so if you installed PostgreSQL in a
! location that is not searched by default, you have to add an option
! such as -I/usr/local/pgsql/include to the
! compilation command line.
--- 771,781 ----
cc -c prog1.c
The generated C source files include headers files from the
! PostgreSQL installation, so if you installed
! PostgreSQL in a location that is not searched by
! default, you have to add an option such as
! -I/usr/local/pgsql/include to the compilation
! command line.
Index: doc/src/sgml/features.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/features.sgml,v
retrieving revision 2.7
diff -c -r2.7 features.sgml
*** doc/src/sgml/features.sgml 21 Sep 2002 18:32:53 -0000 2.7
--- doc/src/sgml/features.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 15,25 ****
! SQL99 defines a large set of individual
! features rather than the ineffectively broad three levels found in
SQL92. We provide a list of supported features,
! followed by a list of the features defined in SQL99 which are not
! yet supported in PostgreSQL.
--- 15,26 ----
! SQL99 defines a large set of individual features
! rather than the ineffectively broad three levels found in
SQL92. We provide a list of supported features,
! followed by a list of the features defined in
! SQL99 which are not yet supported in
! PostgreSQL.
Index: doc/src/sgml/info.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/info.sgml,v
retrieving revision 1.16
diff -c -r1.16 info.sgml
*** doc/src/sgml/info.sgml 24 Oct 2002 17:48:54 -0000 1.16
--- doc/src/sgml/info.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 6,12 ****
Overview of Documentation Resources
! The PostgreSQL documentation is organized into several books:
--- 6,13 ----
Overview of Documentation Resources
! The PostgreSQL documentation is organized into
! several books:
***************
*** 22,30 ****
&cite-user;
! Documents the SQL query language environment, including data
! types and functions, as well as user-level performance tuning.
! Every PostgreSQL user should read this.
--- 23,32 ----
&cite-user;
! Documents the SQL query language environment,
! including data types and functions, as well as user-level
! performance tuning. Every PostgreSQL user
! should read this.
***************
*** 34,41 ****
Installation and server management information. Everyone who
! runs a PostgreSQL server, either for personal use or for other
! users, needs to read this.
--- 36,43 ----
Installation and server management information. Everyone who
! runs a PostgreSQL server, either for personal
! use or for other users, needs to read this.
***************
*** 55,63 ****
&cite-reference;
! Reference pages for SQL command syntax, and client and server
! programs. This book is auxiliary to the User's,
! Administrator's, and Programmer's Guides.
--- 57,65 ----
&cite-reference;
! Reference pages for SQL command syntax, and
! client and server programs. This book is auxiliary to the
! User's, Administrator's, and Programmer's Guides.
Index: doc/src/sgml/installation.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/installation.sgml,v
retrieving revision 1.112
diff -c -r1.112 installation.sgml
*** doc/src/sgml/installation.sgml 12 Nov 2002 20:19:55 -0000 1.112
--- doc/src/sgml/installation.sgml 14 Nov 2002 01:14:47 -0000
***************
*** 68,76 ****
make programs will not work.
GNU make is often installed under
the name gmake; this document will always
! refer to it by that name. (On some systems GNU make is the
! default tool with the name make.) To test for
! GNU make enter
gmake --version
--- 68,77 ----
make programs will not work.
GNU make is often installed under
the name gmake; this document will always
! refer to it by that name. (On some systems
! GNU make is the default tool with the name
! make.) To test for GNU
! make enter
gmake --version
***************
*** 137,145 ****
To build the server programming language PL/Perl you need a full
! Perl installation, including the libperl
! library and the header files. Since PL/Perl will be a shared
! library, the libperllibperl library must be a shared library
also on most platforms. This appears to be the default in
recent Perl versions, but it was not in earlier versions, and in
--- 138,147 ----
To build the server programming language PL/Perl you need a full
! Perl installation, including the
! libperl library and the header files.
! Since PL/Perl will be a shared library, the
! libperllibperl library must be a shared library
also on most platforms. This appears to be the default in
recent Perl versions, but it was not in earlier versions, and in
***************
*** 198,205 ****
url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ
3.30. On some operating systems you don't really have
to build a shared library, but then you will have to convince
! the PostgreSQL build system of this. Consult the
! Makefile in the
src/pl/plpython directory for details.
--- 200,207 ----
url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ
3.30. On some operating systems you don't really have
to build a shared library, but then you will have to convince
! the PostgreSQL build system of this. Consult
! the Makefile in the
src/pl/plpython directory for details.
***************
*** 250,267 ****
To enable Native Language Support (NLS), that
is, the ability to display a program's messages in a language
! other than English, you need an implementation of the Gettext
! API. Some operating systems have this
! built-in (e.g., Linux, NetBSD, Solaris), for other systems you can download
! an add-on package from here: .
If you are using the gettext implementation in
! the GNU C library then you will additionally need the
! GNU Gettext package for some utility
! programs. For any of the other implementations you will not
! need it.
--- 252,269 ----
To enable Native Language Support (NLS), that
is, the ability to display a program's messages in a language
! other than English, you need an implementation of the
! Gettext API. Some operating
! systems have this built-in (e.g., Linux, NetBSD,
! Solaris), for other systems you
! can download an add-on package from here: .
If you are using the gettext implementation in
! the GNU C library then you will additionally
! need the GNU Gettext package for some
! utility programs. For any of the other implementations you will
! not need it.
***************
*** 276,284 ****
! If you are build from a CVS tree instead of using a released source
! package, or if you want to do development, you also need the
! following packages:
--- 278,286 ----
! If you are build from a CVS tree instead of
! using a released source package, or if you want to do development,
! you also need the following packages:
***************
*** 1257,1264 ****
add /usr/local/pgsql/bin (or whatever you set
--- 1259,1266 ----
add /usr/local/pgsql/bin (or whatever you set
Index: doc/src/sgml/jdbc.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/jdbc.sgml,v
retrieving revision 1.40
diff -c -r1.40 jdbc.sgml
*** doc/src/sgml/jdbc.sgml 11 Nov 2002 07:31:28 -0000 1.40
--- doc/src/sgml/jdbc.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 51,66 ****
! Alternatively you can build the driver from source, but you
! should only need to do this if you are making changes to the
! source code. For details, refer to the PostgreSQL installation
instructions. After installation, the driver should be found in
PREFIX/share/java/postgresql.jar.
The resulting driver will be built for the version of Java you are
! running. If you build with a 1.1 JDK you will build a version
! that supports the JDBC 1 specification, if you build with a Java 2
! JDK (e.g., JDK 1.2 or JDK 1.3) you will build a version that
! supports the JDBC 2 specification.
--- 51,67 ----
! Alternatively you can build the driver from source, but you should
! only need to do this if you are making changes to the source code.
! For details, refer to the PostgreSQL installation
instructions. After installation, the driver should be found in
PREFIX/share/java/postgresql.jar.
The resulting driver will be built for the version of Java you are
! running. If you build with a 1.1 JDK you will build a
! version that supports the JDBC 1 specification, if you build with
! a Java 2 JDK (e.g., JDK 1.2 or
! JDK 1.3) you will build a version that supports the
! JDBC 2 specification.
Index: doc/src/sgml/libpgtcl.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/libpgtcl.sgml,v
retrieving revision 1.32
diff -c -r1.32 libpgtcl.sgml
*** doc/src/sgml/libpgtcl.sgml 8 Nov 2002 04:56:40 -0000 1.32
--- doc/src/sgml/libpgtcl.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 1112,1118 ****
Description
! pg_execute submits a query to the PostgreSQL backend.
If the query is not a SELECT statement, the query is executed and the
--- 1112,1119 ----
Description
! pg_execute submits a query to the
! PostgreSQL backend.
If the query is not a SELECT statement, the query is executed and the
Index: doc/src/sgml/libpq.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/libpq.sgml,v
retrieving revision 1.101
diff -c -r1.101 libpq.sgml
*** doc/src/sgml/libpq.sgml 11 Nov 2002 20:14:03 -0000 1.101
--- doc/src/sgml/libpq.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 957,968 ****
PQescapeBytea returns an escaped version of the
! from parameter binary string, to a caller-provided
! buffer. The return string has all special characters replaced
! so that they can be properly processed by the PostgreSQL string literal
! parser, and the bytea input function. A terminating zero
! byte is also added. The single quotes that must surround
! PostgreSQL string literals are not part of the result string.
--- 957,970 ----
PQescapeBytea returns an escaped version of the
! from parameter binary string, to a
! caller-provided buffer. The return string has all special
! characters replaced so that they can be properly processed by the
! PostgreSQL string literal parser, and the
! bytea input function. A terminating zero byte is also
! added. The single quotes that must surround
! PostgreSQL string literals are not part of the
! result string.
Index: doc/src/sgml/manage-ag.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/manage-ag.sgml,v
retrieving revision 2.23
diff -c -r2.23 manage-ag.sgml
*** doc/src/sgml/manage-ag.sgml 11 Nov 2002 20:14:03 -0000 2.23
--- doc/src/sgml/manage-ag.sgml 14 Nov 2002 01:01:28 -0000
***************
*** 8,32 ****
database
! Every instance of a running PostgreSQL server manages one or more
! databases. Databases are therefore the topmost hierarchical level
! for organizing SQL objects (database objects). This
! chapter describes the properties of databases, and how to create,
! manage, and destroy them.
Overview
! A database is a named collection of SQL objects (database
! objects). Generally, every database object (tables,
! functions, etc.) belongs to one and only one database. (But there
! are a few system catalogs, for example pg_database,
! that belong to a whole installation and are accessible from each
! database within the installation.) More accurately, a database is
! a collection of schemas and the schemas contain the tables,
! functions, etc. So the full hierarchy is:
server, database, schema, table (or something else instead of a
table).
--- 8,33 ----
database
! Every instance of a running PostgreSQL
! server manages one or more databases. Databases are therefore the
! topmost hierarchical level for organizing SQL
! objects (database objects). This chapter describes
! the properties of databases, and how to create, manage, and destroy
! them.
Overview
! A database is a named collection of SQL objects
! (database objects). Generally, every database
! object (tables, functions, etc.) belongs to one and only one
! database. (But there are a few system catalogs, for example
! pg_database, that belong to a whole installation and
! are accessible from each database within the installation.) More
! accurately, a database is a collection of schemas and the schemas
! contain the tables, functions, etc. So the full hierarchy is:
server, database, schema, table (or something else instead of a
table).
***************
*** 41,53 ****
connection. Schemas are a purely logical structure and who can
access what is managed by the privilege system. Databases are
physically separated and access control is managed at the
! connection level. If one PostgreSQL server instance is to house
! projects or users that should be separate and for the most part
! unaware of each other, it is therefore recommendable to put them
! into separate databases. If the projects or users are interrelated
! and should be able to use each other's resources they should be put
! in the same databases but possibly into separate schemas. More
! information about managing schemas is in the &cite-user;.
--- 42,55 ----
connection. Schemas are a purely logical structure and who can
access what is managed by the privilege system. Databases are
physically separated and access control is managed at the
! connection level. If one PostgreSQL server
! instance is to house projects or users that should be separate and
! for the most part unaware of each other, it is therefore
! recommendable to put them into separate databases. If the projects
! or users are interrelated and should be able to use each other's
! resources they should be put in the same databases but possibly
! into separate schemas. More information about managing schemas is
! in the &cite-user;.
***************
*** 73,83 ****
CREATE DATABASE name
! where name follows the usual rules for SQL identifiers.
! The current user automatically becomes
! the owner of the new database. It is the privilege of the owner of
! a database to remove it later on (which also removes all the
! objects in it, even if they have a different owner).
--- 75,85 ----
CREATE DATABASE name
! where name follows the usual rules for
! SQL identifiers. The current user automatically
! becomes the owner of the new database. It is the privilege of the
! owner of a database to remove it later on (which also removes all
! the objects in it, even if they have a different owner).
***************
*** 262,271 ****
Database Configuration
! Recall from that the PostgreSQL
! server provides a large number of run-time configuration variables.
! You can set database-specific default values for many of these
! settings.
--- 264,273 ----
Database Configuration
! Recall from that the
! PostgreSQL server provides a large number of
! run-time configuration variables. You can set database-specific
! default values for many of these settings.
Index: doc/src/sgml/mvcc.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/mvcc.sgml,v
retrieving revision 2.29
diff -c -r2.29 mvcc.sgml
*** doc/src/sgml/mvcc.sgml 11 Nov 2002 20:14:03 -0000 2.29
--- doc/src/sgml/mvcc.sgml 14 Nov 2002 01:16:50 -0000
***************
*** 10,21 ****
! This chapter describes the behavior of the PostgreSQL database
! system when two or more sessions try to access the same data at the
! same time. The goals in that situation are to allow efficient
! access for all sessions while maintaining strict data integrity.
! Every developer of database applications should be familiar with
! the topics covered in this chapter.
--- 10,22 ----
! This chapter describes the behavior of the
! PostgreSQL database system when two or
! more sessions try to access the same data at the same time. The
! goals in that situation are to allow efficient access for all
! sessions while maintaining strict data integrity. Every developer
! of database applications should be familiar with the topics covered
! in this chapter.
***************
*** 38,53 ****
The main difference between multiversion and lock models is that
! in MVCC locks acquired for querying (reading) data don't conflict
! with locks acquired for writing data, and so reading never blocks
! writing and writing never blocks reading.
Table- and row-level locking facilities are also available in
PostgreSQL for applications that cannot
! adapt easily to MVCC behavior. However, proper use of MVCC will
! generally provide better performance than locks.
--- 39,55 ----
The main difference between multiversion and lock models is that
! in MVCC locks acquired for querying (reading)
! data don't conflict with locks acquired for writing data, and so
! reading never blocks writing and writing never blocks reading.
Table- and row-level locking facilities are also available in
PostgreSQL for applications that cannot
! adapt easily to MVCC behavior. However, proper
! use of MVCC will generally provide better
! performance than locks.
***************
*** 380,393 ****
PostgreSQL provides various lock modes
! to control concurrent access to data in tables. These modes can be
! used for application-controlled locking in situations where MVCC
! does not give the desired behavior. Also, most
! PostgreSQL commands automatically
! acquire locks of appropriate modes to ensure that referenced tables
! are not dropped or modified in incompatible ways while the command
! executes. (For example, ALTER TABLE cannot be executed
! concurrently with other operations on the same table.)
--- 382,395 ----
PostgreSQL provides various lock modes
! to control concurrent access to data in tables. These modes can
! be used for application-controlled locking in situations where
! MVCC does not give the desired behavior. Also,
! most PostgreSQL commands automatically
! acquire locks of appropriate modes to ensure that referenced
! tables are not dropped or modified in incompatible ways while the
! command executes. (For example, ALTER TABLE cannot be
! executed concurrently with other operations on the same table.)
***************
*** 725,731 ****
! Global validity checks require extra thought under MVCC. For
example, a banking application might wish to check that the sum of
all credits in one table equals the sum of debits in another table,
when both tables are being actively updated. Comparing the results of two
--- 727,733 ----
! Global validity checks require extra thought under MVCC. For
example, a banking application might wish to check that the sum of
all credits in one table equals the sum of debits in another table,
when both tables are being actively updated. Comparing the results of two
Index: doc/src/sgml/programmer.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/programmer.sgml,v
retrieving revision 1.43
diff -c -r1.43 programmer.sgml
*** doc/src/sgml/programmer.sgml 24 Oct 2002 17:48:54 -0000 1.43
--- doc/src/sgml/programmer.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 24,41 ****
What's In This Book
! This book is for PostgreSQL application programmers. It is divided into three parts.
The first part of this book describes the client programming
! interfaces distributed with PostgreSQL. Each of these chapters
! can be read independently. Note that there are many other
! programming interfaces for client programs that are distributed
! separately and contain their own documentation. Readers of the
! first part should be familiar with using SQL commands to
! manipulate and query the database (see the &cite-user;) and of
! course with the programming language that the interface uses.
--- 24,43 ----
What's In This Book
! This book is for PostgreSQL application
! programmers. It is divided into three parts.
The first part of this book describes the client programming
! interfaces distributed with PostgreSQL. Each of
! these chapters can be read independently. Note that there are
! many other programming interfaces for client programs that are
! distributed separately and contain their own documentation.
! Readers of the first part should be familiar with using
! SQL commands to manipulate and query the
! database (see the &cite-user;) and of course with the programming
! language that the interface uses.
***************
*** 43,49 ****
functionality with user-defined functions, data types, triggers,
etc. These are advanced topics which should probably be
approached only after all the other user documentation about
! PostgreSQL has been understood.
--- 45,51 ----
functionality with user-defined functions, data types, triggers,
etc. These are advanced topics which should probably be
approached only after all the other user documentation about
! PostgreSQL has been understood.
Index: doc/src/sgml/syntax.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/syntax.sgml,v
retrieving revision 1.73
diff -c -r1.73 syntax.sgml
*** doc/src/sgml/syntax.sgml 11 Nov 2002 20:14:04 -0000 1.73
--- doc/src/sgml/syntax.sgml 14 Nov 2002 01:23:17 -0000
***************
*** 120,127 ****
The system uses no more than NAMEDATALEN-1
characters of an identifier; longer names can be written in
commands, but they will be truncated. By default,
! NAMEDATALEN is 64 so the maximum identifier length
! is 63 (but at the time PostgreSQL is built,
NAMEDATALEN can be changed in
src/include/postgres_ext.h).
--- 120,127 ----
The system uses no more than NAMEDATALEN-1
characters of an identifier; longer names can be written in
commands, but they will be truncated. By default,
! NAMEDATALEN is 64 so the maximum identifier
! length is 63 (but at the time PostgreSQL is built,
NAMEDATALEN can be changed in
src/include/postgres_ext.h).
***************
*** 652,666 ****
shows the precedence and
! associativity of the operators in PostgreSQL. Most operators have
! the same precedence and are left-associative. The precedence and
! associativity of the operators is hard-wired into the parser.
! This may lead to non-intuitive behavior; for example the Boolean
! operators < and > have a different
! precedence than the Boolean operators <= and
! >=. Also, you will sometimes need to add
! parentheses when using combinations of binary and unary operators.
! For instance
SELECT 5 ! - 6;
--- 652,666 ----
shows the precedence and
! associativity of the operators in PostgreSQL.
! Most operators have the same precedence and are left-associative.
! The precedence and associativity of the operators is hard-wired
! into the parser. This may lead to non-intuitive behavior; for
! example the Boolean operators < and
! > have a different precedence than the Boolean
! operators <= and >=. Also, you will
! sometimes need to add parentheses when using combinations of
! binary and unary operators. For instance
SELECT 5 ! - 6;
Index: doc/src/sgml/tutorial.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/tutorial.sgml,v
retrieving revision 1.17
diff -c -r1.17 tutorial.sgml
*** doc/src/sgml/tutorial.sgml 24 Oct 2002 17:48:54 -0000 1.17
--- doc/src/sgml/tutorial.sgml 14 Nov 2002 01:20:41 -0000
***************
*** 30,38 ****
these aspects. We only assume some general knowledge about how to
use computers. No particular Unix or programming experience is
required. This book is mainly intended to give you a hands-on
! experience with important aspects of the PostgreSQL system. It
! makes no attempt to be a complete or thorough treatment of the
! topics it covers.
--- 30,38 ----
these aspects. We only assume some general knowledge about how to
use computers. No particular Unix or programming experience is
required. This book is mainly intended to give you a hands-on
! experience with important aspects of the
! PostgreSQL system. It makes no attempt
! to be a complete or thorough treatment of the topics it covers.
Index: doc/src/sgml/user.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/user.sgml,v
retrieving revision 1.34
diff -c -r1.34 user.sgml
*** doc/src/sgml/user.sgml 11 Nov 2002 20:14:04 -0000 1.34
--- doc/src/sgml/user.sgml 14 Nov 2002 01:02:55 -0000
***************
*** 23,35 ****
What's In This Book
! This book describes the use of the SQL language in PostgreSQL. We
! start with describing the general syntax of SQL, then explain how
! to create the structures to hold data, how to populate the
! database, and how to query it. The middle part lists the
! available data types and functions for use in SQL data commands.
! The rest of the book treats several aspects that are important for
! tuning a database for optimal performance.
--- 23,37 ----
What's In This Book
! This book describes the use of the SQL language
! in PostgreSQL. We start with
! describing the general syntax of SQL, then
! explain how to create the structures to hold data, how to populate
! the database, and how to query it. The middle part lists the
! available data types and functions for use in
! SQL data commands. The rest of the book treats
! several aspects that are important for tuning a database for
! optimal performance.
***************
*** 44,53 ****
! Readers of this book should know how to connect to a PostgreSQL
! database and issue SQL commands. Readers that are unfamiliar with
! these issues are encouraged to read the &cite-tutorial; first. SQL
! commands are typically entered using the PostgreSQL interactive
terminal psql, but other programs that
have similar functionality can be used as well.
--- 46,55 ----
! Readers of this book should know how to connect to a PostgreSQL
! database and issue SQL commands. Readers that are unfamiliar with
! these issues are encouraged to read the &cite-tutorial; first. SQL
! commands are typically entered using the PostgreSQL interactive
terminal psql, but other programs that
have similar functionality can be used as well.
Index: doc/src/sgml/xfunc.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/xfunc.sgml,v
retrieving revision 1.61
diff -c -r1.61 xfunc.sgml
*** doc/src/sgml/xfunc.sgml 21 Sep 2002 18:32:54 -0000 1.61
--- doc/src/sgml/xfunc.sgml 14 Nov 2002 01:22:42 -0000
***************
*** 674,680 ****
! The user ID the PostgreSQL server runs
as must be able to traverse the path to the file you intend to
load. Making the file or a higher-level directory not readable
and/or not executable by the postgres user is a
--- 674,680 ----
! The user ID the PostgreSQL server runs
as must be able to traverse the path to the file you intend to
load. Making the file or a higher-level directory not readable
and/or not executable by the postgres user is a
***************
*** 691,697 ****
! PostgreSQL will not compile a C function
automatically. The object file must be compiled before it is referenced
in a CREATE
FUNCTION command. See for additional
--- 691,697 ----
! PostgreSQL will not compile a C function
automatically. The object file must be compiled before it is referenced
in a CREATE
FUNCTION command. See for additional
***************
*** 721,727 ****
! Before PostgreSQL release 7.2, only exact
absolute paths to object files could be specified in CREATE
FUNCTION. This approach is now deprecated since it makes the
function definition unnecessarily unportable. It's best to specify
--- 721,727 ----
! Before PostgreSQL release 7.2, only exact
absolute paths to object files could be specified in CREATE
FUNCTION. This approach is now deprecated since it makes the
function definition unnecessarily unportable. It's best to specify
Index: doc/src/sgml/ref/create_cast.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/create_cast.sgml,v
retrieving revision 1.6
diff -c -r1.6 create_cast.sgml
*** doc/src/sgml/ref/create_cast.sgml 4 Oct 2002 22:08:44 -0000 1.6
--- doc/src/sgml/ref/create_cast.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 196,209 ****
! Prior to PostgreSQL 7.3, every function that had the same name as a
! data type, returned that data type, and took one argument of a
! different type was automatically a cast function. This convention has
! been abandoned in face of the introduction of schemas and to be
! able to represent binary compatible casts in the catalogs. (The built-in
! cast functions
! still follow this naming scheme, but they have to be shown as
! casts in pg_cast now.)
--- 196,209 ----
! Prior to PostgreSQL 7.3, every function that had
! the same name as a data type, returned that data type, and took one
! argument of a different type was automatically a cast function.
! This convention has been abandoned in face of the introduction of
! schemas and to be able to represent binary compatible casts in the
! catalogs. (The built-in cast functions still follow this naming
! scheme, but they have to be shown as casts in pg_cast
! now.)
Index: doc/src/sgml/ref/create_database.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/create_database.sgml,v
retrieving revision 1.29
diff -c -r1.29 create_database.sgml
*** doc/src/sgml/ref/create_database.sgml 21 Sep 2002 18:32:54 -0000 1.29
--- doc/src/sgml/ref/create_database.sgml 14 Nov 2002 01:18:06 -0000
***************
*** 217,223 ****
name. In particular,
by writing TEMPLATE = template0, you can create a virgin
database containing only the standard objects predefined by your
! version of PostgreSQL. This is useful
if you wish to avoid copying
any installation-local objects that may have been added to
template1.
--- 217,223 ----
name. In particular,
by writing TEMPLATE = template0, you can create a virgin
database containing only the standard objects predefined by your
! version of PostgreSQL. This is useful
if you wish to avoid copying
any installation-local objects that may have been added to
template1.
Index: doc/src/sgml/ref/ecpg-ref.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/ecpg-ref.sgml,v
retrieving revision 1.22
diff -c -r1.22 ecpg-ref.sgml
*** doc/src/sgml/ref/ecpg-ref.sgml 24 Oct 2002 17:48:54 -0000 1.22
--- doc/src/sgml/ref/ecpg-ref.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 157,165 ****
When compiling the preprocessed C code files, the compiler needs to
be able to find the ECPG header files in the
! PostgreSQL include directory. Therefore, one might have to use the
!
--- 157,165 ----
When compiling the preprocessed C code files, the compiler needs to
be able to find the ECPG header files in the
! PostgreSQL include directory. Therefore, one might
! have to use the
Index: doc/src/sgml/ref/explain.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/explain.sgml,v
retrieving revision 1.20
diff -c -r1.20 explain.sgml
*** doc/src/sgml/ref/explain.sgml 21 Apr 2002 19:02:39 -0000 1.20
--- doc/src/sgml/ref/explain.sgml 14 Nov 2002 01:19:23 -0000
***************
*** 87,93 ****
! Prior to PostgreSQL 7.3, the query plan
was emitted in the form of a NOTICE message. Now it appears as a
query result (formatted like a table with a single text column).
--- 87,93 ----
! Prior to PostgreSQL 7.3, the query plan
was emitted in the form of a NOTICE message. Now it appears as a
query result (formatted like a table with a single text column).
***************
*** 105,116 ****
This command displays the execution plan that the
! PostgreSQL planner
! generates for the supplied query. The execution plan shows how
! the table(s) referenced by the query will be scanned---by plain
! sequential scan, index scan, etc.---and if multiple tables are
! referenced, what join algorithms will be used to bring together
! the required tuples from each input table.
--- 105,116 ----
This command displays the execution plan that the
! PostgreSQL planner generates for the
! supplied query. The execution plan shows how the table(s)
! referenced by the query will be scanned---by plain sequential scan,
! index scan, etc.---and if multiple tables are referenced, what join
! algorithms will be used to bring together the required tuples from
! each input table.
***************
*** 156,162 ****
The VERBOSE option emits the full internal representation of the plan tree,
rather than just a summary.
Usually this option is only useful for debugging
! PostgreSQL. The VERBOSE dump is either
pretty-printed or not, depending on the setting of the
configuration parameter.
--- 156,162 ----
The VERBOSE option emits the full internal representation of the plan tree,
rather than just a summary.
Usually this option is only useful for debugging
! PostgreSQL. The VERBOSE dump is either
pretty-printed or not, depending on the setting of the
configuration parameter.
***************
*** 232,238 ****
Note that the specific numbers shown, and even the selected query
! strategy, may vary between PostgreSQL
releases due to planner improvements.
--- 232,238 ----
Note that the specific numbers shown, and even the selected query
! strategy, may vary between PostgreSQL
releases due to planner improvements.
Index: doc/src/sgml/ref/load.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/load.sgml,v
retrieving revision 1.12
diff -c -r1.12 load.sgml
*** doc/src/sgml/ref/load.sgml 20 Jan 2002 22:19:57 -0000 1.12
--- doc/src/sgml/ref/load.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 23,35 ****
Description
! Loads a shared library file into the PostgreSQL backend's address
! space. If the file had been loaded previously, it is first
! unloaded. This command is primarily useful to unload and reload a
! shared library file that has been changed since the backend first
! loaded it. To make use of the
! shared library, function(s) in it need to be declared using the command.
--- 23,36 ----
Description
! Loads a shared library file into the PostgreSQL
! backend's address space. If the file had been loaded previously,
! it is first unloaded. This command is primarily useful to unload
! and reload a shared library file that has been changed since the
! backend first loaded it. To make use of the shared library,
! function(s) in it need to be declared using the
! command.
Index: doc/src/sgml/ref/pg_config-ref.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v
retrieving revision 1.11
diff -c -r1.11 pg_config-ref.sgml
*** doc/src/sgml/ref/pg_config-ref.sgml 11 Oct 2002 23:03:48 -0000 1.11
--- doc/src/sgml/ref/pg_config-ref.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 131,137 ****
The option is new in
! PostgreSQL 7.2. In prior releases, the server include files were
installed in the same location as the client headers, which could
be queried with the . To make your
package handle both cases, try the newer option first and test the
--- 131,137 ----
The option is new in
! PostgreSQL 7.2. In prior releases, the server include files were
installed in the same location as the client headers, which could
be queried with the . To make your
package handle both cases, try the newer option first and test the
***************
*** 139,145 ****
! In releases prior to PostgreSQL 7.1, before the
pg_config came to be, a method for finding the
equivalent configuration information did not exist.
--- 139,145 ----
! In releases prior to PostgreSQL 7.1, before the
pg_config came to be, a method for finding the
equivalent configuration information did not exist.
***************
*** 150,156 ****
History
! The pg_config utility first appeared in PostgreSQL 7.1.
--- 150,157 ----
History
! The pg_config utility first appeared in
! PostgreSQL 7.1.
Index: doc/src/sgml/ref/pg_dump.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_dump.sgml,v
retrieving revision 1.52
diff -c -r1.52 pg_dump.sgml
*** doc/src/sgml/ref/pg_dump.sgml 11 Oct 2002 23:03:48 -0000 1.52
--- doc/src/sgml/ref/pg_dump.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 274,284 ****
pg_dump can handle databases from
! previous releases of PostgreSQL, but very old versions are not
! supported anymore (currently prior to 7.0). Use this option
! if you need to override the version check (and if
! pg_dump then fails, don't say you
! weren't warned).
--- 274,284 ----
pg_dump can handle databases from
! previous releases of PostgreSQL, but very old
! versions are not supported anymore (currently prior to 7.0).
! Use this option if you need to override the version check (and
! if pg_dump then fails, don't say
! you weren't warned).
***************
*** 289,295 ****
Dump object identifiers (OIDs) for every
! table. Use this option if your application references the OID
columns in some way (e.g., in a foreign key constraint).
Otherwise, this option should not be used.
--- 289,295 ----
Dump object identifiers (OIDs) for every
! table. Use this option if your application references the OID
columns in some way (e.g., in a foreign key constraint).
Otherwise, this option should not be used.
Index: doc/src/sgml/ref/pg_dumpall.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_dumpall.sgml,v
retrieving revision 1.34
diff -c -r1.34 pg_dumpall.sgml
*** doc/src/sgml/ref/pg_dumpall.sgml 7 Sep 2002 16:14:33 -0000 1.34
--- doc/src/sgml/ref/pg_dumpall.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 27,39 ****
pg_dumpall is a utility for writing out
! (dumping) all PostgreSQL databases of a cluster into
! one script file. The script file contains SQL commands that can be
! used as input to
! to restore the databases. It does this by calling for each database
! in a cluster. pg_dumpall also dumps
! global objects that are common to all databases.
(pg_dump does not save these objects.)
This currently includes the information about database users and
groups.
--- 27,39 ----
pg_dumpall is a utility for writing out
! (dumping) all PostgreSQL databases
! of a cluster into one script file. The script file contains
! SQL commands that can be used as input to to restore the databases. It does this by
! calling for each database in a cluster.
! pg_dumpall also dumps global objects
! that are common to all databases.
(pg_dump does not save these objects.)
This currently includes the information about database users and
groups.
***************
*** 139,149 ****
pg_dumpall can handle databases
! from previous releases of PostgreSQL, but very old versions
! are not supported anymore (currently prior to 7.0). Use this
! option if you need to override the version check (and if
! pg_dumpall then fails, don't say
! you weren't warned).
--- 139,149 ----
pg_dumpall can handle databases
! from previous releases of PostgreSQL, but very
! old versions are not supported anymore (currently prior to
! 7.0). Use this option if you need to override the version
! check (and if pg_dumpall then
! fails, don't say you weren't warned).
Index: doc/src/sgml/ref/pg_restore.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_restore.sgml,v
retrieving revision 1.31
diff -c -r1.31 pg_restore.sgml
*** doc/src/sgml/ref/pg_restore.sgml 11 Oct 2002 23:03:48 -0000 1.31
--- doc/src/sgml/ref/pg_restore.sgml 14 Nov 2002 00:47:15 -0000
***************
*** 417,427 ****
! Presently, the commands emitted for
--- 417,428 ----
! Presently, the commands emitted for
!
***************
*** 522,533 ****
pg_restore could not attach to the
! PostgreSQL server
! process on the specified host and port. If you see this message,
! ensure that the server
! is running on the proper host and that you have specified the proper
! port. If your site uses an authentication system, ensure that you
! have obtained the required authentication credentials.
--- 523,534 ----
pg_restore could not attach to the
! PostgreSQL server process on the specified
! host and port. If you see this message, ensure that the
! server is running on the proper host and that you have
! specified the proper port. If your site uses an
! authentication system, ensure that you have obtained the
! required authentication credentials.
***************
*** 537,543 ****
When a direct database connection is specified using the -d
option, pg_restore internally executes
! SQL statements. If you have problems running
pg_restore, make sure you are able to select
information from the database using, for example,
psql.
--- 538,544 ----
When a direct database connection is specified using the -d
option, pg_restore internally executes
! SQL statements. If you have problems running
pg_restore, make sure you are able to select
information from the database using, for example,
psql.