Re: ToDo List Item - System Table Index Clustering - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ToDo List Item - System Table Index Clustering
Date
Msg-id AANLkTim5AF3OgccirvNP7kiaQkTvazWMmD+aXRkaQse1@mail.gmail.com
Whole thread Raw
In response to Re: ToDo List Item - System Table Index Clustering  ("Simone Aiken" <saiken@ulfheim.net>)
List pgsql-hackers
On Wed, Jan 19, 2011 at 4:27 PM, Simone Aiken <saiken@ulfheim.net> wrote:
> In my experience size increases related to documentation are almost always
> worth it.  So I'm prejudiced right out of the gate.  I was wondering if
> every pg_ table gets copied out to every database ..  if there is already a
> mechanism for not replicating all of them we could utilize views or
> re-writes rules to merge a single copy of catalog comments in a separate
> table with each deployed database's pg_descriptions.

All of them get copied, except for a handful of so-called shared
catalogs.  Changing that would be difficult.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER TYPE 1: recheck index-based constraints
Next
From: Alvaro Herrera
Date:
Subject: Re: sepgsql contrib module