Обсуждение: log activity questions

Поиск
Список
Период
Сортировка

log activity questions

От
Marc Fromm
Дата:

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.

 

Also there are these fatal entries:

FATAL:  database "template0" is not currently accepting connections

FATAL:  database "template0" is not currently accepting connections

 

What is the transaction ID wrap and should I change a setting to correct them?

Does the template need to accept connections? If I make a new database based on template0 does that mean that database cannot accept connections?

 

Thanks

 

Marc

 

Re: log activity questions

От
"Scott Marlowe"
Дата:
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.

Re: log activity questions

От
Tom Lane
Дата:
"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