I successfully did the pg_dumpall from the 9.2 server (separate box) of the 8.1 server. After restoring the dumped file the blank entries remain.
Marc
From: Keith [mailto:keith@keithf4.com] Sent: Monday, May 04, 2015 8:18 AM To: Marc Fromm Cc: Raghavendra; Keith Fiske; pgsql-admin@postgresql.org Subject: Re: [ADMIN] migrating to 9.2 created blank dbs
Going by your package name, I'm assuming you're running Red Hat or CentOS. Running both 8.1 and 9.2 at the same time on that OS could be a bit tricky and this isn't really the proper medium for discussing how to do so.
What you could do is copy the 9.2 pg_dumpall binary from the machine you have it installed on now and put it on the other machine. As long as they're the same OS/architecture that should work fine. The other option is to open up a network connection between the two systems and allow pg_dumpall from the 9.2 system to connect to 8.1 on the old system.
I setup a server running postgresql-server-9.2.10-2.el7_1.x86_64. After restoring my databases form a system running postgresql-server-8.1.23-10.el5_10 (created with pg_dumpall), several blank databases/entries were created.
When I list the database from the command line it shows several entries like:
| | | | | =T/postgres
After importing the databases is there a cleanup command of some sort?
These blank databases/entries do not show in PhpPgAdmin, yet my backup script tries to backup a database called “|”
Is this behaviour, after you have imported the databases and ANALYZE cluster ?. By-chance if you have missed to performe ANALYZE on post import, please do it.
Did you run the 9.2 version of pg_dumpall or the 8.1 version to create your original dump file? You should run the 9.2 version on the 8.1 database if possible.
