| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, 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:38:45 |
| Message-ID: | CA+TgmoZkgifHN+LxFVehjsU0q=v7zfz2usM6gO6BVbbY4SR08g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 27, 2011 at 11:35 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> What about creating a new, single-purpose database in the source
>> cluster and then removing it again after we're done?
>
> That is not a problem --- I can easily use template1.
Huh?
You just said upthread that you didn't want to use template1 because
you didn't want to modify the template database. I think the point is
that if you're doing something to the database that someone might
object to, you oughtn't be doing it to the postgres database either.
You should create a database just for pg_upgrade's use and install its
crap in there.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-10-28 03:41:01 | Re: pg_upgrade if 'postgres' database is dropped |
| Previous Message | Bruce Momjian | 2011-10-28 03:35:36 | Re: pg_upgrade if 'postgres' database is dropped |