pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Albe Laurenz <laurenz.albe@wien.gv.at>
Cc: 'Guo, Yun *EXTERN*' <YGuo@cvent.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_dump not dumping some schemas
Date: Tue, 02 Jun 2015 10:22:51 -0400
Message-ID: <28315.1433254971@sss.pgh.pa.us> (raw)
In-Reply-To: <A737B7A37273E048B164557ADEF4A58B3661B848@ntex2010i.host.magwien.gv.at>
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>
	<D1928D1D.378F4%yguo@cvent.com>
	<11998.1433214088@sss.pgh.pa.us>
	<D19329C5.37A5E%yguo@cvent.com>
	<A737B7A37273E048B164557ADEF4A58B3661B848@ntex2010i.host.magwien.gv.at>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Albe Laurenz <laurenz.albe@wien.gv.at> writes:
> Yun Guo wrote:
>> polling_etl=# SELECT classid, objid, refclassid, refobjid
>> FROM pg_depend
>> WHERE refclassid = 'pg_extension'::regclass
>> AND deptype = 'e'  and objid = 17972
>> ORDER BY 3,4;
>> classid | objid | refclassid | refobjid
>> ---------+-------+------------+----------
>> 2615 | 17972 |       3079 |    16730
>> 
>> polling_etl=# select * from pg_extension where oid = 16730;
>> extname | extowner | extnamespace | extrelocatable | extversion |
>> extconfig | extcondition
>> ---------+----------+--------------+----------------+------------+---------
>> --+--------------
>> hstore  |       10 |        16389 | t              | 1.2        |
>> |
>> 
>> How can I remove this dependency? Or what should I do to make it dump the
>> schema creation correctly?

> It *is* being dumped correctly.

Indeed.  What's more interesting to ask is how did the hstore extension
wind up owning a schema?  That should certainly not happen as shipped.
Were you playing around with ALTER EXTENSION ADD/DROP?

			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



view thread (19+ messages)  latest in thread

Message-ID: <28315.1433254971@sss.pgh.pa.us>
Permalink:  ../28315.1433254971@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28315.1433254971@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, laurenz.albe@wien.gv.at, YGuo@cvent.com
  Subject: Re: pg_dump not dumping some schemas
  In-Reply-To: <28315.1433254971@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox