Re: Unused system table columns

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unused system table columns
Date: 2002-07-16 05:04:52
Message-ID: 1026795892.1939.18.camel@rh72.home.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2002-07-16 at 11:44, Tom Lane wrote:
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
> > The interim solution would be to set typreceive/typsend to NULL if they
> > are the same as typinput/typoutput in CREATE TYPE.
>
> Which still puts you right back at square one. You might as well define
> two new columns that will carry the function names for binary transport.

Ok, but could this be then rename instead of removing the columns - it
will be roughly the same amount of work going through all the places
that touch pg_type. I'd even guess that renaming is _less_ work..

> typsend/typreceive are hopelessly contaminated at this point, IMHO;
> it'll be less work and less confusion to adopt other column names than
> to try to reuse them just "because they're there".

-----------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-16 05:15:10 Re: DROP COLUMN
Previous Message Bruce Momjian 2002-07-16 05:04:24 Re: DROP COLUMN