| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> | 
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us> | 
| Subject: | pg_upgrade if 'postgres' database is dropped | 
| Date: | 2011-10-04 16:11:12 | 
| Message-ID: | 4E8B3020.4060002@enterprisedb.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
pg_upgrade doesn't work if the 'postgres' database has been dropped in 
the old cluster:
~/pgsql.master$ bin/pg_upgrade -b ~/pgsql.91stable/bin -B bin/ -d 
~/pgsql.91stable/data -D data-upgraded/
Performing Consistency Checks
-----------------------------
Checking current, bin, and data directories                 ok
Checking cluster versions                                   ok
Checking database user is a superuser                       ok
Checking for prepared transactions                          ok
Checking for reg* system OID user data types                ok
Checking for contrib/isn with bigint-passing mismatch       ok
Creating catalog dump                                       ok
Checking for prepared transactions                          ok
New cluster database "postgres" does not exist in the old cluster
Failure, exiting
That's a bit unfortunate. We have some other tools that don't work 
without the 'postgres' database, like 'reindexdb -all', but it would 
still be nice if pg_upgrade did.
-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-04 16:23:17 | Re: Should we get rid of custom_variable_classes altogether? | 
| Previous Message | Dimitri Fontaine | 2011-10-04 15:17:07 | Re: Should we get rid of custom_variable_classes altogether? |