perpetual dump/restore problem

From: wu_zhong_min(at)vrane(dot)com
To: pgsql-general(at)postgresql(dot)org
Subject: perpetual dump/restore problem
Date: 2007-07-04 21:43:57
Message-ID: 20070704214357.BDEBC214002@ftp.a
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear List,

As many of you know every time one wants to upgrade to a major server version, as I want to do now, there is a need for pg_dumpall and restore. This is a huge undertaking and requires lots of testing and planning. I do hope that in the future this requirement will be dropped.

I am now upgrading from 8.1.9 to 8.2.4 and pg_dumpall gives a dump file which has a command "\connect template0"

Normally template0 does not accept connection but I found a way to make that happen in the documentation on postgresql website. But is it generally safe to accept the connection for template0 all the time? Why won't pg_dump include a line to accept connection for template0 just before it writes "\connect template0" and then remove the permission after it is done with template0?

thanks

Wu Z-m

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2007-07-04 22:04:35 Re: Problem with autovacuum and pg_autovacuum
Previous Message Andreas 'ads' Scherbaum 2007-07-04 21:42:53 Problem with autovacuum and pg_autovacuum