Catalog Bloat in Development - Frequently dropping/adding schemas and objects - Mailing list pgsql-general

From David Johnston
Subject Catalog Bloat in Development - Frequently dropping/adding schemas and objects
Date
Msg-id 020301cd5638$28943010$79bc9030$@yahoo.com
Whole thread Raw
Responses Re: Catalog Bloat in Development - Frequently dropping/adding schemas and objects  (Ben Madin <lists@remoteinformation.com.au>)
List pgsql-general

In my current development environment I often drop some or all of the schemas in the database and then re-create them schemas and the objects they contain.  When I go to bring up the database in my GUI it takes a considerable amount of time to initialize.  I suspect this is because the catalog tables are becoming bloated.  What is the recommended course of action to de-bloat them?  Running an unqualified vacuum does not seem to help.  Is it better to just periodically drop and recreate the database itself or would a vacuum with specific tables listed be sufficient – and if so which tables?

 

Thanks!

 

David J.

pgsql-general by date:

Previous
From: Andy Chambers
Date:
Subject: Promotion of standby to master
Next
From: Misa Simic
Date:
Subject: LEFT and RIGHT JOIN