Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M44080=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1YzQZR-00077a-Ol
 for pgsql-admin@arkaria.postgresql.org; Mon, 01 Jun 2015 14:20:05 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M44080=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1YzQZR-00056s-7r
 for pgsql-admin@arkaria.postgresql.org; Mon, 01 Jun 2015 14:20:05 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <tgl@sss.pgh.pa.us>) id 1YzQZQ-000554-9w
 for pgsql-admin@postgresql.org; Mon, 01 Jun 2015 14:20:04 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
 by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
 (Exim 4.84) (envelope-from <tgl@sss.pgh.pa.us>) id 1YzQZN-0002YD-JF
 for pgsql-admin@postgresql.org; Mon, 01 Jun 2015 14:20:03 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
 by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t51EJxCD017197;
 Mon, 1 Jun 2015 10:19:59 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Guo, Yun" <YGuo@cvent.com>
cc: "'Albe Laurenz'" <laurenz.albe@wien.gv.at>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: pg_dump not dumping some schemas
In-reply-to: <2DB6C5478F692C4C983B3129CC1AEB14CA65E8C8@HQ08HQMX002.cvent.net>
References: <D18CC6E9.36A0E%yguo@cvent.com>
 <A737B7A37273E048B164557ADEF4A58B36617951@ntex2010i.host.magwien.gv.at>
 <D18DE04B.36C72%yguo@cvent.com>
 <A737B7A37273E048B164557ADEF4A58B36618A43@ntex2010i.host.magwien.gv.at>
 <D191D463.3774F%yguo@cvent.com>
 <A737B7A37273E048B164557ADEF4A58B36618F30@ntex2010i.host.magwien.gv.at>
 <2DB6C5478F692C4C983B3129CC1AEB14CA65E8C8@HQ08HQMX002.cvent.net>
Comments: In-reply-to "Guo, Yun" <YGuo@cvent.com>
 message dated "Mon, 01 Jun 2015 14:12:10 -0000"
Date: Mon, 01 Jun 2015 10:19:59 -0400
Message-ID: <17196.1433168399@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.5 (-)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

"Guo, Yun" <YGuo@cvent.com> writes:
> Is there a way to repair the database if it's corrupted?

There's no evidence here that you've got any server-side corruption.
pg_dump should be getting back the exact same results you got
manually.

(BTW, I assume you've ruled out the possibility that pg_dump is connecting
to some other server or database than the one you're looking at
manually...)

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin