Re: migrating to 9.2 created blank dbs - Mailing list pgsql-admin

From Marc Fromm
Subject Re: migrating to 9.2 created blank dbs
Date
Msg-id SN1PR0201MB15663C77E1FD1FFB3CA0DE049DD20@SN1PR0201MB1566.namprd02.prod.outlook.com
Whole thread Raw
In response to Re: migrating to 9.2 created blank dbs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: migrating to 9.2 created blank dbs
List pgsql-admin
Running the select statement gives me a list of all my databases. The only thing that looks suspicious are a few
databaseshave stuff like this in the datacl column " {postgres=CT/postgres,=T/postgres}". The number of databases with
thatis suspiciously equal to the number of blanks created. 

Marc

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, May 04, 2015 9:07 AM
To: Keith
Cc: Marc Fromm; Raghavendra; Keith Fiske; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] migrating to 9.2 created blank dbs

> On Fri, May 1, 2015 at 6:39 PM, Marc Fromm <Marc.Fromm@wwu.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.
Ifthe 8.1 server is still online it would be interesting to connect to it manually and see what you get from "select *
frompg_database". 

            regards, tom lane


pgsql-admin by date:

Previous
From: Mel Llaguno
Date:
Subject: Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times
Next
From: Jeff Frost
Date:
Subject: Re: migrating to 9.2 created blank dbs