DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type;
	b=tXP6vgXi7+AFUKN9J87rs/x9y86JfilycrtdUoQRY2K/VKJpZ1tW8KmCcWUU5B+yz42lXgJiL/sTnZpbMf59XYY2RaooaWrw1Xr4fkBJCP1s2A/zPiLWG7a2z/VHtFxLdRG2s2icP+aRQgpZRQQVWrE7q4qlTSVfBGLht/1k5/Q=;
Message-ID: <1328015852.22615.YahooMailClassic@web161404.mail.bf1.yahoo.com>
Date: Tue, 31 Jan 2012 05:17:32 -0800 (PST)
From: chester c young <chestercyoung@yahoo.com>
Subject: pg_dump not correctly saving schema with partitioned tables?
To: pgsql-sql@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

have database with many partitions.  each partition table has its own primary key sequence.

   Column  ||                          Modifiers                           
-----------++--------------------------------------------------------------
 uno_id    || not null default nextval('cmp0004.cmt_uno_id_seq'::regclass)

when dumped and then resorted, the pk sequence is changed to an inherited- from table:


    Column    ||                      Modifiers                       
--------------++------------------------------------------------------
 uno_id       || not null default nextval('uno_uno_id_seq'::regclass)

(another error is that the pk sequence does not spec the schema!)

is there any way I can reliably backup and restore the db?