Re: Catalogs design question - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Catalogs design question
Date
Msg-id Pine.LNX.4.30.0110201333430.827-100000@peter.localdomain
Whole thread Raw
In response to Re: Catalogs design question  ("Steve Howe" <howe@carcass.dhs.org>)
List pgsql-hackers
Steve Howe 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 ?
> That's far from perfect, but at least would solve those issues and others
> which might appear in other catalogs...

In general, the system catalogs are far from a perfect example (or even an
example at all) for pure, normalized relational database design.  A more
important concern in processing efficiency.  For instance, currently the
execution of a procedure takes one catalog lookup versus (1 + nargs) in a
more normalized design.  (This is an oversimplification, but you get the
idea.)

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: Unable to upgrade to 7.2
Next
From: darcy@druid.net (D'Arcy J.M. Cain)
Date:
Subject: Re: pg_sorttemp files