Date: Wed, 29 Feb 2012 15:55:13 -0500
From: Ray Stell <stellr@cns.vt.edu>
To: pgsql-admin@postgresql.org
Subject: re-create information_schema
Message-ID: <20120229205513.GA761@cns.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)

on rebuilding the information_schema:
http://www.postgresql.org/docs/9.1/static/release-9-1-2.html
...
Since the view definition is installed by initdb, merely upgrading will
not fix the problem. If you need to fix this in an existing installation,
you can (as a superuser) drop the information_schema schema then re-create
it by sourcing SHAREDIR/information_schema.sql. (Run pg_config --sharedir
if you're uncertain where SHAREDIR is.) This must be repeated in each
database to be fixed.


The right thing to do here is drop cascade, correct?  No harm done with 
that?

doodah=# drop schema information_schema;
ERROR:  cannot drop schema information_schema because other objects depend on it
DETAIL:  table information_schema.sql_sizing_profiles depends on schema information_schema
table information_schema.sql_sizing depends on schema information_schema
...
view information_schema.check_constraint_routine_usage column constraint_name depends on type information_schema.sql_identifier
and 138 other objects (see server log for list)
HINT:  Use DROP ... CASCADE to drop the dependent objects too.

Thanks.