Re: Catalogs design question

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Steve Howe" <howe(at)carcass(dot)dhs(dot)org>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Catalogs design question
Date: 2001-10-20 16:42:28
Message-ID: 12806.1003596148@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Steve Howe" <howe(at)carcass(dot)dhs(dot)org> writes:
>> The group array is a hack but the pg_proc array would be hard to replace
>> becauseit acts as part of the unique key used for cache lookups.

> This design itself bothers me.
> We have no other option left ? Like arrays being referenced in relations ?

Sure, it *could* be done another way. As far as pg_proc goes, I agree
with Bruce: there are far too many places that know the existing
representation for us to consider changing it. The pain involved would
vastly outweigh any possible benefit.

The representation of groups is not so widely known, however. We could
probably get away with changing it, if someone wanted to propose a
better catalog schema and do the legwork to make it happen.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-10-20 16:46:18 Re: Unable to upgrade to 7.2
Previous Message Bruce Momjian 2001-10-20 16:42:24 Re: To Postgres Devs : Wouldn't changing the select limit