head	1.6;
access;
symbols;
locks; strict;
comment	@# @;


1.6
date	93.01.26.02.43.13;	author aoki;	state Exp;
branches;
next	1.5;

1.5
date	92.07.13.03.45.59;	author ptong;	state Exp;
branches;
next	1.4;

1.4
date	91.08.16.06.30.39;	author mao;	state Exp;
branches;
next	1.3;

1.3
date	91.02.22.17.39.21;	author mike;	state Exp;
branches;
next	1.2;

1.2
date	90.07.19.18.31.23;	author claire;	state Exp;
branches;
next	1.1;

1.1
date	90.07.18.16.16.28;	author mao;	state Exp;
branches;
next	;


desc
@description of postgres 'template' database
@


1.6
log
@-man version
@
text
@.\" This is -*-nroff-*-
.\" XXX standard disclaimer belongs here....
.\" $Header: /home2/aoki/ref/files/RCS/template.8,v 1.5 1992/07/13 03:45:59 ptong Exp aoki $
.TH TEMPLATE FILES 01/23/93
.XA 1 Template
.SH NAME
\&.../data/files/global1.bki \(em global database template
.br
\&.../data/files/local1_XXX.bki \(em local database template
.br
\&.../data/files/template1/* \(em default database template
.SH DESCRIPTION
These files contain scripts which direct the construction of
databases.  Note that the \*(lqglobal1.bki\*(rq and
\*(lqtemplate1_local.bki\*(rq files are installed automatically when
the \*(PG super-user runs
.IR initdb .
These files are copied from
.(C
\&.../src/backend/obj/{dbdb,local}.bki
.)C
The databases which are generated by the template scripts are normal
databases.  Consequently, you can use the terminal monitor or some
other frontend on a template database to simplify the customization
task.  That is, there is no need to express everything about your
desired initial database state using a BKI template script, because
the database state can be tuned interactively.
.PP
The system catalogs consist of classes of two types: global and local.
There is one copy of each global class that is shared among all
databases at a site.  Local classes, on the other hand, are not
accessible except from their own database.
.PP
The file
.(C
\&.../data/files/global1.bki
.)C
specifies the process used in the creation of global (shared) classes
by
.IR createdb .
Similarly, the
.(C
\&.../files/local1_XXX.bki
.)C
files specify the process used in the creation of local (unshared)
catalog classes for the \*(lqXXX\*(rq template database.
\*(lqXXX\*(rq may be any string of 16 or fewer printable characters.
If no template is specified in a
.IR createdb
command,
then the template in
.(C
\&.../files/local1_template1.bki
.)C
is used.
.PP
The .bki files are generated from C source code by an inscrutable set
of AWK scripts.
.SH BUGS
\*(PG Version \*(PV does not permit users to have separate template
databases.
.SH "SEE ALSO"
bki(files),
initdb(unix),
createdb(unix).
@


1.5
log
@Fixed up formating
@
text
@d1 1
d3 2
a4 2
.\" $Header: /home/postgres/mer/refs/files/RCS/template,v 1.4 1991/08/16 06:30:39 mao Exp ptong $
.SP TEMPLATE FILES 6/14/90
d6 2
a7 3
.uh NAME
.lp
\&.../files/global1.bki \*- global database template
d9 9
a17 8
\&.../files/local1_XXX.bki \*- local database template
.uh DESCRIPTION
.lp
These files contain scripts
which direct the construction of databases.
Note that the global1.bki and template1_local.bki files
are installed automatically when the postgres superuser runs
.b initdb .
d19 20
a38 24
.q .../src/support/{dbdb,local}.bki.
.lp
The databases which are generated by the template scripts
are normal databases.
Consequently,
you can use the terminal monitor or some other frontend
on a template database to simplify the
customization task.
That is, 
there is no need to
express everything about
your desired initial database state
using a BKI template script,
because the database state can be
tuned interactively.
.lp
The system catalogs consist of classes of two types:  global and local.
There is one copy of each global class that is shared
among all databases at a site.
Local classes, on the other hand, are not accessible
except from their own database.
.lp
\&.../files/global1.bki specifies the
process used in the creation of global (shared) classes
d40 1
a40 1
.b createdb .
d42 6
a47 7
\&.../files/local1_XXX.bki files specify the
process used in the creation of local (unshared) catalog classes
for the
.q XXX
template database.
.q XXX
may be any string of 16 or fewer printable characters.
d49 14
a62 10
.b createdb command,
then the template in .../files/local1_template1.bki is used.
.lp
The .bki files are generated from C source code by an inscrutable
set of C preprocessor macros.
.uh BUGS
.lp
\*(PP Version \*(PV does not permit users to have separate template databases.
.uh "SEE ALSO"
.lp
@


1.4
log
@rel 3
@
text
@d2 1
a2 1
.\" $Header: /local/mao/postgres/ref/files/RCS/template,v 1.3 1991/02/22 17:39:21 mike Exp mao $
d60 1
a60 2
Release 3.0 does not permit users to have separate template
databases.
@


1.3
log
@objectified
@
text
@d2 1
a2 1
.\" $Header: RCS/template,v 1.2 90/07/19 18:31:23 claire Exp Locker: mike $
d16 1
a16 2
.q "createdb postgres"
for the first time.
d30 2
a31 2
using an AMI template script,
but the database state can be
d56 3
a58 1
The .bki files are generated from C source code in Version 2.1.
d60 2
d65 2
a66 1
createdb(unix)
@


1.2
log
@*** empty log message ***
@
text
@d2 1
a2 1
.\" $Header: RCS/template,v 1.1 90/07/18 16:16:28 mao Exp Locker: claire $
d35 2
a36 2
The system catalogs consist of relations of two types:  global and local.
There is one copy of each global relation that is shared
d38 1
a38 1
Local relations, on the other hand, are not accessible
d42 1
a42 1
process used in the creation of global (shared) relations
d47 1
a47 1
process used in the creation of local (unshared) catalog relations
d57 1
a57 1
The .bki files are generated from C source code in Version 2.
@


1.1
log
@Initial revision
@
text
@d2 1
a2 1
.\" $Header: template,v 1.6 89/04/20 13:23:39 wensel Exp $
d27 1
a27 1
I.e.,
d53 2
a54 1
If no template is specified in a createdb command,
@