From: | Kasia Tuszynska <ktuszynska(at)esri(dot)com> |
---|---|
To: | David Johnston <polobo(at)yahoo(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: looking for doc |
Date: | 2014-03-18 16:14:09 |
Message-ID: | 6C308A1FFB24664F8636F3B58ABEF84588719A7D@RED-INF-EXMB-P2.esri.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
David J,
If the whole purpose of a template is to be a basis for an additional user database than what admi tasks are defined in template 1 and template 0 does matter, because if template 0 would never be used as a db in it's own right, it's descendants would be.
For instance:
Template 0 does not contain the language encodings and collation settings specific to the os on which postgres is running template 1 does, so if you want to create a db with language settings other than what is in template 1 you would use template 0, and if template 0 does not contain "admin tasks" than it would have to be administered manually....
Sincerely,
Kasia
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of David Johnston
Sent: Monday, March 17, 2014 3:33 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] looking for doc
David Johnston wrote
> 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.
If you are referring to instructions to perform cluster-wide maintenance (i.e., create data, create role) while connected to the "template1" database that it mostly a matter of convenience. template0 should not be used (if it even can be connected to) for administrative tasks because template1 has to exist and is better suited from a logical standpoint to fulfill that role.
The postgres default database is also a viable candidate but often people will drop it if they feel it is not useful.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/looking-for-doc-tp5796445p5796462.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2014-03-18 16:29:52 | Re: looking for doc |
Previous Message | Gilberto Castillo | 2014-03-18 14:38:06 | Re: pg_upgrade in primary/standby architecture |