Re: documentation vs reality: template databases

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: "Richard P(dot) Welty" <rwelty(at)averillpark(dot)net>, Postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Re: documentation vs reality: template databases
Date: 2007-01-22 02:48:17
Message-ID: 200701220248.l0M2mHt23084@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > For example, one could drop <literal>template1</> and recreate it from
> > <literal>template0</> without any ill effects. This course of action
> > might be advisable if one has carelessly added a bunch of junk in
> > ! <literal>template1</>. (To delete <literal>template1</literal>,
> > ! it must have <literal>datistemplate = false</>.)
> > </para>
>
> I don't find this particularly clear -- how does the user know where to
> set the "datistemplate" it refers to? I guess you should mention
> pg_database, or be more explicit about what to do.

OK, it is now:

<literal>template1</>. (To delete <literal>template1</literal>,
it must have <literal>pg_database.datistemplate = false</>.)

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-01-22 03:04:04 Re: More grist for the PostgreSQL vs MySQL mill
Previous Message Shashank Tripathi 2007-01-22 02:30:40 Re: More grist for the PostgreSQL vs MySQL mill