From: Scott Marlowe <scott.marlowe@gmail.com>
To: 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 18:38:16 -0600
Message-ID: <dcc563d10810141738p2cd9efe2gfbc3a3ad099ddfe@mail.gmail.com> (raw)
In-Reply-To: <B0D7C0A3F35FE144A70312D086CBCA9BF76D2C69@ExchMailbox2.univ.dir.wwu.edu>
References: <AckqQMtkvH65+VFZQHO0uDhMtB76rg==>
<B0D7C0A3F35FE144A70312D086CBCA9BF76D2C69@ExchMailbox2.univ.dir.wwu.edu>
On Thu, Oct 9, 2008 at 12:56 PM, Marc Fromm <Marc.Fromm@wwu.edu> wrote:
> I started logging on our server. There are many entries like this:
>
> transaction ID wrap limit is 1073768178, limited by database "postgres"
>
> transaction ID wrap limit is 1073771864, limited by database "sms"
>
> Each database has several of the above entries.
That's completely normal. IT's an information log, not a warning or an error.
> Also there are these fatal entries:
>
> FATAL: database "template0" is not currently accepting connections
>
> FATAL: database "template0" is not currently accepting connections
>
> Does the template need to accept connections? If I make a new database based
> on template0 does that mean that database cannot accept connections?
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.
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: scott.marlowe@gmail.com, Marc.Fromm@wwu.edu
Subject: Re: log activity questions
In-Reply-To: <dcc563d10810141738p2cd9efe2gfbc3a3ad099ddfe@mail.gmail.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