Re: Unused pg_class columns

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unused pg_class columns
Date: 2001-05-30 15:42:24
Message-ID: 200105301542.f4UFgOP03816@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Pgaccess is referencing system columns that are never set.
>
> I wasn't aware that our standard procedure upon finding a bug was to rip
> out the feature, rather than fixing the bug ... this could make life a
> *lot* simpler.

Attached is a patch of all my pgaccess changes this morning. If someone
wants to code the hasprimary test, feel free. You can look at psql to
see new code that does tests for primary keys. It was recently
committed to CVS.

If people would prefer me to comment out the primary key display rather
than remove it, I can do that.

> If relhaspkey isn't set by table creation, then let's set it. Easy
> enough, and it seems like a clearly useful column. As for the other
> columns at issue, those are not ancient history: they were added in
> release 6.4, by Vadim according to the CVS logs. Perhaps you should ask
> him what they are intended for, rather than assuming that they are fair
> game for removal.

I only marked as "not used", not as "remove me". Seems clear enough.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Attachment Content-Type Size
unknown_filename text/plain 3.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-05-30 16:15:02 Re: PL/pgSQL CURSOR support
Previous Message Peter Eisentraut 2001-05-30 15:39:42 Re: Unused pg_class columns