Re: ToDo List Item - System Table Index Clustering

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simone Aiken <saiken(at)ulfheim(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ToDo List Item - System Table Index Clustering
Date: 2011-01-20 14:27:38
Message-ID: AANLkTim5AF3OgccirvNP7kiaQkTvazWMmD+aXRkaQse1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 19, 2011 at 4:27 PM, Simone Aiken <saiken(at)ulfheim(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-01-20 14:59:34 Re: sepgsql contrib module
Previous Message Robert Haas 2011-01-20 14:26:29 Re: ALTER TYPE 1: recheck index-based constraints