diff options
author | Bruce Momjian <bruce@momjian.us> | 2004-10-18 02:56:42 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2004-10-18 02:56:42 +0000 |
commit | b303739c064f938a60bb93b746759abaee229bf5 (patch) | |
tree | a11244c7f53bdc21bd8875853106174572c0367d | |
parent | 301d6e419c62fdf0546a4753054cc9367554b93b (diff) | |
download | postgresql-b303739c064f938a60bb93b746759abaee229bf5.tar.gz postgresql-b303739c064f938a60bb93b746759abaee229bf5.zip |
Add:
>
> * Allow a database in tablespace t1 with tables created in tablespace t2
> to be used as a template for a new database created with default
> tablespace t2
>
> All objects in the default database tablespace must have default tablespace
> specifications. This is because new databases are created by copying
> directories. If you mix default tablespace tables and tablespace-specified
> tables in the same directory, creating a new database from such a mixed
> directory would create a new database with tables that had incorrect
> explicit tablespaces. To fix this would require modifying pg_class in the
> newly copied database, which we don't currently do.
-rw-r--r-- | doc/TODO | 14 |
1 files changed, 13 insertions, 1 deletions
@@ -5,7 +5,7 @@ TODO list for PostgreSQL Bracketed items "[]" have more detail. Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) -Last updated: Thu Oct 14 18:17:50 EDT 2004 +Last updated: Sun Oct 17 22:56:37 EDT 2004 The most recent version of this document can be viewed at the PostgreSQL web site, http://www.PostgreSQL.org. @@ -57,6 +57,18 @@ Administration in their original locations. If this fails, the user must be able to adjust the restore process. +* Allow a database in tablespace t1 with tables created in tablespace t2 + to be used as a template for a new database created with default + tablespace t2 + + All objects in the default database tablespace must have default tablespace + specifications. This is because new databases are created by copying + directories. If you mix default tablespace tables and tablespace-specified + tables in the same directory, creating a new database from such a mixed + directory would create a new database with tables that had incorrect + explicit tablespaces. To fix this would require modifying pg_class in the + newly copied database, which we don't currently do. + * Add "include file" functionality in postgresql.conf * Add session start time and last statement time to pg_stat_activity * Allow server logs to be remotely read using SQL commands |