From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade if 'postgres' database is dropped |
Date: | 2011-10-28 03:22:13 |
Message-ID: | 12407.1319772133@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Stephen Frost wrote:
>> Yes, they would have removed it because they didn't want it. As I
>> recall, part of the agreement to create an extra database by default was
>> that it could be removed if users didn't want it. Turning around and
>> then saying "but things won't work if it's not there" isn't exactly
>> supporting users who decide to remove it.
> Well, you would have to remove it _after_ you did the pg_upgrade.
As far as the *target* cluster is concerned, I have no sympathy for
someone who messes with its contents before running pg_upgrade.
That's an RTFM matter: you're supposed to upgrade into a virgin
just-initdb'd cluster.
However, it would be nice if pg_upgrade supported transferring from a
*source* cluster that didn't have the postgres DB.
What about creating a new, single-purpose database in the source
cluster and then removing it again after we're done?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-10-28 03:35:36 | Re: pg_upgrade if 'postgres' database is dropped |
Previous Message | Bruce Momjian | 2011-10-28 03:19:17 | Re: pg_upgrade if 'postgres' database is dropped |