Re: Create database bug in 8.1.3 ? - Mailing list pgsql-general

From Florian G. Pflug
Subject Re: Create database bug in 8.1.3 ?
Date
Msg-id 443BDEE2.6080902@phlo.org
Whole thread Raw
In response to Create database bug in 8.1.3 ?  ("Milen Kulev" <makulev@gmx.net>)
List pgsql-general
Milen Kulev wrote:
> Hi Listers,
> I have the following problem (OS= RHELU2 , PG version= 8.1.3) when I  try to Create a database :
>
> postgres=# CREATE  DATABASE   world3 TEMPLATE=template1 ENCODING='UTF8' TABLESPACE=tbs1 ;
> CREATE DATABASE
>
> Then I am backup-ing the database (a small toy DB) with pg_dumpall:
>
>  pg_dumpall   > alldb.bak
>
> Less    alldb.bak:
> --------------------
> ....
> CREATE DATABASE world3 WITH TEMPLATE = template0 OWNER = pg ENCODING = 'UTF8' TABLESPACE = tbs1; ....
> --------------------
>
> Why pg_dumpall is stating that my template db is template0 and not template1 ? Is there any way to check what db
> (template0  or template1 ) was actually used a template when creating world2 db ? I am having the same problem  with
all
> my  databases
Why exactly is this a problem? Everything that you might have manually added to template1 is now part
of world3 anyway, and therfore included in the dump of world3. When recreating world3 from the dump,
starting from an completly empty database (template0) makes sense for me - otherwise you'd get lots
of "... already exists" error, because pg_dump would try to restore some objects which already exist in
the newly created world3-version, because they were (again!) inherited from template1.

greetings, Florian Pflug

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Restoring a PITR backup
Next
From: Scott Ribe
Date:
Subject: Re: sound index