Re: pg_upgrade failing from 9.3 to 9.4 because "template0" already exists

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Matt Landry <lelnet(dot)matt(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade failing from 9.3 to 9.4 because "template0" already exists
Date: 2015-03-06 21:20:05
Message-ID: 6376.1425676805@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Matt Landry (lelnet(dot)matt(at)gmail(dot)com) wrote:
>> postgres=# select datname, datallowconn from pg_database ;
>> datname | datallowconn
>> -----------+--------------
>> template1 | t
>> template0 | t
>> postgres | t
>> reporting | t
>> (4 rows)

> Right, as I mentioned, template0 shouldn't have datallowconn as 'true'.
> That's why it's being included in the pg_dumpall.

Perhaps pg_upgrade should deliberately ignore template0 regardless of
datallowconn? And/or we should hard-wire that into pg_dumpall?
I feel no compulsion whatsoever to preserve any user-initiated changes
in template0 across an upgrade.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2015-03-06 21:35:57 Re: pg_upgrade failing from 9.3 to 9.4 because "template0" already exists
Previous Message Matt Landry 2015-03-06 21:14:46 Re: pg_upgrade failing from 9.3 to 9.4 because "template0" already exists