Re: Catalogs design question

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
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 11:45:22
Message-ID: Pine.LNX.4.30.0110201333430.827-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-10-20 11:46:15 Re: To Postgres Devs : Wouldn't changing the select limit
Previous Message D'Arcy J.M. Cain 2001-10-20 11:44:20 Re: pg_sorttemp files