From: "Guo, Yun" <YGuo@cvent.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: 'Albe Laurenz' <laurenz.albe@wien.gv.at>, "pgsql-admin@postgresql.org"
 <pgsql-admin@postgresql.org>
Subject: Re: pg_dump not dumping some schemas
Thread-Topic: [ADMIN] pg_dump not dumping some schemas
Thread-Index: 
 AQHQmWrG8qD1Kd5wwECxQFQUQc4hUJ2SmSMwgABZZgCABFkg4IAAXWMAgAAHsYCAAAXooIAARaiAgACLsgA=
Date: Tue, 2 Jun 2015 02:39:59 +0000
Message-ID: <D1928D1D.378F4%yguo@cvent.com>
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>
 <17196.1433168399@sss.pgh.pa.us>
In-Reply-To: <17196.1433168399@sss.pgh.pa.us>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.5.0.150423
Content-Type: text/plain; charset="us-ascii"
Content-ID: <08D5135FF4B99A49A18DA2C1FBF7602B@cvent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi Tom,

I tried gdb on selectDumpableNamespace() and dumpNamespace().
So it looks like for those problematic schemas,the dump value is 1 in
selectDumpableNamespace() which is correct, but when it goes to
dumpNamespace() the dump value becomes 0, so it get skipped.

Breakpoint 2, selectDumpableNamespace (nsinfo=3D0x6600c0) at pg_dump.c:1227
(gdb) p nsinfo.dobj
$17 =3D {objType =3D DO_NAMESPACE, catId =3D {tableoid =3D 2615, oid =3D 17=
972},
dumpId =3D 13, name =3D 0x660d80 "test", namespace =3D 0x0,
  dump =3D 1 '\001', ext_member =3D 0 '\000', dependencies =3D 0x0, nDeps =
=3D 0,
allocDeps =3D 0}


Breakpoint 1, dumpNamespace (fout=3D0x654290, nspinfo=3D0x6600c0) at
pg_dump.c:7930
7930	{
(gdb)  p nspinfo.dobj
$31 =3D {objType =3D DO_NAMESPACE, catId =3D {tableoid =3D 2615, oid =3D 17=
972},
dumpId =3D 13, name =3D 0x660d80 "test", namespace =3D 0x0,
  dump =3D 0 '\000', ext_member =3D 1 '\001', dependencies =3D 0x6e2b60, nD=
eps =3D
1, allocDeps =3D 16}


What could possibly change the dump value between selectDumpableNamespace
and dumpNamespace ?


On 6/1/15, 10:19 AM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:

>"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


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