Re: looking for doc - Mailing list pgsql-admin

Kasia Tuszynska wrote
> Ian,
> Thanks that is the really only doc that comes up when I search for this.
> It discusses how to call a template to create a new db, but it does not
> list the differences between them. I am going to try to just find a
> definition of both.
> Thanks,
> Kasia
>
> -----Original Message-----
> From: Ian Lawrence Barwick [mailto:

> barwick@

> ]
> Sent: Monday, March 17, 2014 2:52 PM
> To: Kasia Tuszynska
> Cc:

> pgsql-admin@

> Subject: Re: [ADMIN] looking for doc
>
> 2014-03-18 6:37 GMT+09:00 Kasia Tuszynska <

> ktuszynska@

> >:
>> Admins,
>> I am looking for doc that defines the differences between template 1 and
>> template 0. Specifically, I am looking for a discussion on the presence
>> of admin tasks in template 1 and lack of admin tasks ( such as vacuum) in
>> template 0. I am not able to find doc on this, maybe I am remembering
>> something that is no longer the case.
>
> Is this useful for you?
>
>
> http://www.postgresql.org/docs/current/interactive/manage-ag-templatedbs.html
>
> Regards
>
> Ian Barwick

The only difference between them is semantic.  In fact, as that page says
explicitly, at cluster creation time they are identical.

I will paraphrase the first two paragraphs to see if you understand it
better:

template0 is created upon cluster initialization and should never be
altered.  As a practical matter template1 is then created as a clone of
template0.  The purpose of template1 is to allow for the issuance of an
implicit "CREATE DATABASE %dbname% TEMPLATE = 'template1';" since template1
is the default template and all database creation occurs via template
copying.

Admins can alter template1 to include custom stuff that will then be present
in any database created from it while leaving template0 available for those
situation where those customizations in template1 are not desired (i.e,
CREATE DATABASE dbname0 TEMPLATE = 'template0';)

i do not get what you mean by "admin tasks in template1, not in template0".
If you mean why (assuming you are correct) doesn't the system VACUUM
template0 that would be because it should never change and thus never
require such maintenance.  Since template1 can change it does require
maintenance.

David J.




--
View this message in context: http://postgresql.1045698.n5.nabble.com/looking-for-doc-tp5796445p5796459.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.