From: David Johnston <polobo@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: Re: looking for doc
Date: Mon, 17 Mar 2014 15:33:03 -0700 (PDT)
Message-ID: <1395095583225-5796462.post@n5.nabble.com> (raw)
In-Reply-To: <1395095146819-5796459.post@n5.nabble.com>
References: <6C308A1FFB24664F8636F3B58ABEF845887198E2@RED-INF-EXMB-P2.esri.com>
<CAB8KJ=iArO5sWtj6UB5WAdFQ09p8Zd-Hzd+i70DSOh6whS5TMQ@mail.gmail.com>
<6C308A1FFB24664F8636F3B58ABEF8458871991F@RED-INF-EXMB-P2.esri.com>
<1395095146819-5796459.post@n5.nabble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: polobo@yahoo.com
Subject: Re: looking for doc
In-Reply-To: <1395095583225-5796462.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox