e444d9a966
< The proper solution to this will probably the use of a master/slave < replication solution like Sloney and a connection pooling tool like < pgpool. > The proper solution to this will probably the use of a master/slave > replication solution like Sloney and a connection pooling tool like > pgpool. 114,116c114,116 < You can use any of the master/slave replication servers to use a < standby server for data warehousing. To allow read/write queries to < multiple servers, you need multi-master replication like pgcluster. > You can use any of the master/slave replication servers to use a > standby server for data warehousing. To allow read/write queries to > multiple servers, you need multi-master replication like pgcluster. 166,167c166,167 < Currently large objects entries do not have owners. Permissions can < only be set at the pg_largeobject table level. > Currently large objects entries do not have owners. Permissions can > only be set at the pg_largeobject table level. 173c173 < This requires the TOAST column to be stored EXTERNAL. > This requires the TOAST column to be stored EXTERNAL. 359,360c359,360 < One complexity is whether moving a schema should move all existing < schema objects or just define the location for future object creation. > One complexity is whether moving a schema should move all existing > schema objects or just define the location for future object creation. 364,365c364,365 < Currently non-global system tables must be in the default database < schema. Global system tables can never be moved. > Currently non-global system tables must be in the default database > schema. Global system tables can never be moved. 371,375c371,375 < This might require some background daemon to maintain clustering < during periods of low usage. It might also require tables to be only < paritally filled for easier reorganization. Another idea would < be to create a merged heap/index data file so an index lookup would < automatically access the heap data too. > This might require some background daemon to maintain clustering > during periods of low usage. It might also require tables to be only > paritally filled for easier reorganization. Another idea would > be to create a merged heap/index data file so an index lookup would > automatically access the heap data too. 379,380c379,380 < To do this, determine the ideal cluster index for each system < table and set the cluster setting during initdb. > To do this, determine the ideal cluster index for each system > table and set the cluster setting during initdb. 385,386c385,386 < This requires the use of a savepoint before each COPY line is < processed, with ROLLBACK on COPY failure. > This requires the use of a savepoint before each COPY line is > processed, with ROLLBACK on COPY failure. 395,398c395,398 < This requires using the row ctid to map cursor rows back to the < original heap row. This become more complicated if WITH HOLD cursors < are to be supported because WITH HOLD cursors have a copy of the row < and no FOR UPDATE lock. > This requires using the row ctid to map cursor rows back to the > original heap row. This become more complicated if WITH HOLD cursors > are to be supported because WITH HOLD cursors have a copy of the row > and no FOR UPDATE lock. 405,406c405,406 < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. > Because WITH HOLD cursors exist outside transactions, this allows > them to be listed so they can be closed. 413,415c413,415 < This is useful for returning the auto-generated key for an INSERT. < One complication is how to handle rules that run as part of < the insert. > This is useful for returning the auto-generated key for an INSERT. > One complication is how to handle rules that run as part of > the insert. 422c422 < This is basically the same as SET search_path. > This is basically the same as SET search_path. 426,427c426,427 < This requires a checking function to be called after the server < configuration file is read. > This requires a checking function to be called after the server > configuration file is read. 432c432 < Currently only constants are supported. > Currently only constants are supported. 438,439c438,439 < This requires the cached PL/PgSQL byte code to be invalidated when < an object referenced in the function is changed. > This requires the cached PL/PgSQL byte code to be invalidated when > an object referenced in the function is changed. 512,513c512,513 < Document differences between ecpg and the SQL standard and < information about the Informix-compatibility module. > Document differences between ecpg and the SQL standard and > information about the Informix-compatibility module. |
||
|---|---|---|
| config | ||
| contrib | ||
| doc | ||
| src | ||
| COPYRIGHT | ||
| GNUmakefile.in | ||
| Makefile | ||
| README | ||
| README.CVS | ||
| aclocal.m4 | ||
| configure | ||
| configure.in | ||
README
PostgreSQL Database Management System ===================================== This directory contains the source code distribution of the PostgreSQL database management system. PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions. This distribution also contains C language bindings. The JDBC, ODBC, C++, Python, and Tcl interfaces have been moved to the PostgreSQL Projects Web Site at http://gborg.postgresql.org for separate maintenance. A Perl DBI/DBD driver is available from CPAN. See the file INSTALL for instructions on how to build and install PostgreSQL. That file also lists supported operating systems and hardware platforms and contains information regarding any other software packages that are required to build or run the PostgreSQL system. Changes between all PostgreSQL releases are recorded in the file HISTORY. Copyright and license information can be found in the file COPYRIGHT. A comprehensive documentation set is included in this distribution; it can be read as described in the installation instructions. The latest version of this software may be obtained at ftp://ftp.postgresql.org/pub/. For more information look at our web site located at http://www.postgresql.org/.