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.