Re: Unused system table columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)tm(dot)ee>
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 06:44:25
Message-ID: 10521.1026801865@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-07-16 06:51:41 Re: pg_views.definition
Previous Message Bruce Momjian 2002-07-16 06:29:29 Re: Unused system table columns