Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

PostgreSQL Database Creation-2

  • CREATE DATABASE actually works by copying an existing database. By default, it copies the standard system database named template1. Thus that database is the "template" from which new databases are made. If you add objects to template1, these objects will be copied into subsequently created user databases. This behavior allows site-local modifications to the standard set of objects in databases. For example, if you install the procedural language PL/Perl in template1, it will automatically be available in user databases without any extra action being taken when those databases are created.
  • There is a second standard system database named template0. This database contains the same data as the initial contents of template1, that is, only the standard objects predefined by your version of PostgreSQL. template0 should never be changed after the database cluster has been initialized. By instructing CREATE DATABASE to copy template0 instead of template1, you can create a "virgin" user database that contains none of the site-local additions in template1. This is particularly handy when restoring a pg_dump dump: the dump script should be restored in a virgin database to ensure that one recreates the correct contents of the dumped database, without conflicting with objects that might have been added to template1 later on.
  • Another common reason for copying template0 instead of template1 is that new encoding and locale settings can be specified when copying template0, whereas a copy of template1 must use the same settings it does. This is because template1 might contain encoding-specific or locale-specific data, while template0 is known not to.
create a database coping template0 in sql:
postgres=# create database temp0copy template template0;
CREATE DATABASE
create a database coping template0 in shell:
[postgres@r1 ~]$ createdb -T template0 temp0copy2
Password: 
[postgres@r1 ~]$ 
List the database using command line:
[postgres@r1 ~]$ psql -l
Password: 
                                  List of databases
    Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges   
------------+----------+----------+-------------+-------------+-----------------------
 account    | u1       | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 musicdb    | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 postgres   | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 sales      | u2       | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 temp0copy  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 temp0copy2 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
 template0  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres     
     +
            |          |          |             |             | postgres=CTc/postgres
 template1  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres     
     +
            |          |          |             |             | postgres=CTc/postgres
(8 rows)
  • It is possible to create additional template databases, and indeed one can copy any database in a cluster by specifying its name as the template for CREATE DATABASE. It is important to understand, however, that this is not (yet) intended as a general-purpose "COPY DATABASE" facility. 
  • The principal limitation is that no other sessions can be connected to the source database while it is being copied. CREATE DATABASE will fail if any other connection exists when it starts; during the copy operation, new connections to the source database are prevented.
Two useful flags exist in pg_database for each database: 
  1. datistemplate 
  2. datallowconn
datistemplate:
  • datistemplate can be set to indicate that a database is intended as a template for CREATE DATABASE. 
  • If this flag is set(t), the database can be cloned by any user with CREATEDB privileges; 
  • if it is not set(f), only superusers and the owner of the database can clone it. 
datallowconn :
  • If datallowconn is false, then no new connections to that database will be allowed (but existing sessions are not terminated simply by setting the flag false). The template0 database is normally marked datallowconn = false to prevent its modification. 
  • If true => new connections not disturbed.
  • Both template0 and template1 should always be marked with datistemplate = true.
postgres=#  select datname, datistemplate, datallowconn from pg_database;
  datname   | datistemplate | datallowconn 
------------+---------------+--------------
 template1  | t             | t
 template0  | t             | f
 postgres   | f             | t
 sales      | f             | t
 musicdb    | f             | t
 account    | f             | t
 temp0copy  | f             | t
 temp0copy2 | f             | t
(8 rows)
Notes: template1 and template0 do not have any special status beyond the fact that the name template1 is the default source database name for CREATE DATABASE. 
Example For  one could drop template1 and recreate it from template0 without any ill effects. This course of action might be advisable if one has carelessly added a bunch of junk in template1. (To delete template1, it must have pg_database.datistemplate = false.)

The postgres database is also created when a database cluster is initialized. This database is meant as a default database for users and applications to connect to. It is simply a copy of template1 and can be dropped and recreated if necessary.
Database Configuration:
 PostgreSQL server provides a large number of run-time configuration variables. You can set database-specific default values for many of these settings.
For example, if for some reason you want to disable the GEQO optimizer for a given database, you'd ordinarily have to either disable it for all databases or make sure that every connecting client is careful to issue SET geqo TO off;. To make this setting the default within a particular database, you can execute the command:
ALTER DATABASE mydb SET geqo TO off;
This will save the setting (but not set it immediately). In subsequent connections to this database it will appear as though SET geqo TO off; had been executed just before the session started. Note that users can still alter this setting during their sessions; it will only be the default. To undo any such setting, use ALTER DATABASE dbname RESET varname;.
Destroying a Database
Databases are destroyed with the command DROP DATABASE:
DROP DATABASE name;
  • Only the owner of the database, or a superuser, can drop a database. Dropping a database removes all objects that were contained within the database. The destruction of a database cannot be undone.
  • You cannot execute the DROP DATABASE command while connected to the victim database. You can, however, be connected to any other database, including the template1 database. template1 would be the only option for dropping the last user database of a given cluster.
For convenience, there is also a shell program to drop databases, dropdb:
dropdb dbname
(Unlike createdb, it is not the default action to drop the database with the current user name.)
postgres=# select pg_database_size('account');
 pg_database_size 
------------------
          6349316
(1 row)
postgres=# select pg_size_pretty(pg_database_size('account'));
 pg_size_pretty 
----------------
 6201 kB
(1 row)
                                                                                                           

No comments:

Post a Comment