Re: migrating to 9.2 created blank dbs

Any chance you’re just misinterpreting the new more verbose output of psql’s \l command?

Nowadays, it looks like this:

postgres=# \l
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
---------------+------------+----------+---------+-------+-----------------------
postgres | postgres | UTF8 | C | C |
template0 | postgres | UTF8 | C | C | =c/postgres +
| | | | | postgres=CTc/postgres
template1 | postgres | UTF8 | C | C | =c/postgres +
| | | | | postgres=CTc/postgres
(4 rows)

But there are still only 3 databases being listed above.

> On May 4, 2015, at 9:24 AM, Marc Fromm <Marc(dot)Fromm(at)wwu(dot)edu> wrote:
>
> Running the select statement gives me a list of all my databases. The only thing that looks suspicious are a few databases have stuff like this in the datacl column " {postgres=CT/postgres,=T/postgres}". The number of databases with that is suspiciously equal to the number of blanks created.
>
> Marc
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Monday, May 04, 2015 9:07 AM
> To: Keith
> Cc: Marc Fromm; Raghavendra; Keith Fiske; pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] migrating to 9.2 created blank dbs
>
>> On Fri, May 1, 2015 at 6:39 PM, Marc Fromm <Marc(dot)Fromm(at)wwu(dot)edu> wrote:
>>> 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.
>
> FWIW, this seems to match a symptom we've heard of occasionally in which the source server's catalogs are corrupted. If the 8.1 server is still online it would be interesting to connect to it manually and see what you get from "select * from pg_database”.