From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Marc Fromm <Marc.Fromm@wwu.edu>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: log activity questions
Date: Tue, 14 Oct 2008 20:43:35 -0400
Message-ID: <6592.1224031415@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d10810141738p2cd9efe2gfbc3a3ad099ddfe@mail.gmail.com>
References: <AckqQMtkvH65+VFZQHO0uDhMtB76rg==>
<B0D7C0A3F35FE144A70312D086CBCA9BF76D2C69@ExchMailbox2.univ.dir.wwu.edu>
<dcc563d10810141738p2cd9efe2gfbc3a3ad099ddfe@mail.gmail.com>
"Scott Marlowe" <scott.marlowe@gmail.com> writes:
> Template0 is your "man, I really screwed up template1" get out of jail
> free database. It is normally set to not allow connections (look at
> "select * from pg_databases;" for the field that does or doesn't allow
> connections). If you ever did terrible things to templat1, you could
> set template0 to datallowcon=t and then drop and recreate template1
> using template0 as the template. Then vacuum freeze it and set it to
> not allow connections again to template0 to get it back to normal
> again.
You don't need to (and shouldn't) touch datallowconn while doing the
above. Just use some third database to launch the "DROP DATABASE
template1" and "CREATE DATABASE template1 WITH TEMPLATE template0"
commands.
BTW: the other, more common use of template0 is as a template for making
a database to restore a dump into. If you use template1 then any local
additions in template1 pose a hazard for the dump (which probably also
tries to define those objects).
regards, tom lane
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: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, Marc.Fromm@wwu.edu
Subject: Re: log activity questions
In-Reply-To: <6592.1224031415@sss.pgh.pa.us>
* 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