pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
re-create information_schema
4+ messages / 2 participants
[nested] [flat]

* re-create information_schema
@ 2012-02-29 20:55 Ray Stell <stellr@cns.vt.edu>
  2012-02-29 21:25 ` Re: re-create information_schema Ray Stell <stellr@cns.vt.edu>
  0 siblings, 1 reply; 4+ messages in thread

From: Ray Stell @ 2012-02-29 20:55 UTC (permalink / raw)
  To: pgsql-admin

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.



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: re-create information_schema
  2012-02-29 20:55 re-create information_schema Ray Stell <stellr@cns.vt.edu>
@ 2012-02-29 21:25 ` Ray Stell <stellr@cns.vt.edu>
  2012-03-03 18:27   ` Re: re-create information_schema Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 1 reply; 4+ messages in thread

From: Ray Stell @ 2012-02-29 21:25 UTC (permalink / raw)
  To: pgsql-admin

On Wed, Feb 29, 2012 at 03:55:13PM -0500, Ray Stell wrote:
> http://www.postgresql.org/docs/9.1/static/release-9-1-2.html
> This must be repeated in each
> database to be fixed.

including postgres, template0, and template1?



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: re-create information_schema
  2012-02-29 20:55 re-create information_schema Ray Stell <stellr@cns.vt.edu>
  2012-02-29 21:25 ` Re: re-create information_schema Ray Stell <stellr@cns.vt.edu>
@ 2012-03-03 18:27   ` Peter Eisentraut <peter_e@gmx.net>
  2012-03-03 22:28     ` Re: re-create information_schema Ray Stell <stellr@cns.vt.edu>
  0 siblings, 1 reply; 4+ messages in thread

From: Peter Eisentraut @ 2012-03-03 18:27 UTC (permalink / raw)
  To: Ray Stell <stellr@cns.vt.edu>; +Cc: pgsql-admin

On ons, 2012-02-29 at 16:25 -0500, Ray Stell wrote:
> On Wed, Feb 29, 2012 at 03:55:13PM -0500, Ray Stell wrote:
> > http://www.postgresql.org/docs/9.1/static/release-9-1-2.html
> > This must be repeated in each
> > database to be fixed.
> 
> including postgres, template0, and template1?

Yes, if you want those databases to be fixed.




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: re-create information_schema
  2012-02-29 20:55 re-create information_schema Ray Stell <stellr@cns.vt.edu>
  2012-02-29 21:25 ` Re: re-create information_schema Ray Stell <stellr@cns.vt.edu>
  2012-03-03 18:27   ` Re: re-create information_schema Peter Eisentraut <peter_e@gmx.net>
@ 2012-03-03 22:28     ` Ray Stell <stellr@cns.vt.edu>
  0 siblings, 0 replies; 4+ messages in thread

From: Ray Stell @ 2012-03-03 22:28 UTC (permalink / raw)
  To: Peter Eisentraut <peter_e@gmx.net>; +Cc: pgsql-admin

On Sat, Mar 03, 2012 at 08:27:19PM +0200, Peter Eisentraut wrote:
> On ons, 2012-02-29 at 16:25 -0500, Ray Stell wrote:
> > On Wed, Feb 29, 2012 at 03:55:13PM -0500, Ray Stell wrote:
> > > http://www.postgresql.org/docs/9.1/static/release-9-1-2.html
> > > This must be repeated in each
> > > database to be fixed.
> > 
> > including postgres, template0, and template1?
> 
> Yes, if you want those databases to be fixed.


A trick with template0, or so it seems:

template1=# select datname, datallowconn from pg_database;
  datname  | datallowconn 
-----------+--------------
 template1 | t
 template0 | f
 postgres  | t
 rd        | t
(4 rows)



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2012-03-03 22:28 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-02-29 20:55 re-create information_schema Ray Stell <stellr@cns.vt.edu>
2012-02-29 21:25 ` Ray Stell <stellr@cns.vt.edu>
2012-03-03 18:27   ` Peter Eisentraut <peter_e@gmx.net>
2012-03-03 22:28     ` Ray Stell <stellr@cns.vt.edu>

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