Re: Why does TupleDescInitBuiltinEntry lack a "default: error" case?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Why does TupleDescInitBuiltinEntry lack a "default: error" case?
Date: 2018-12-09 20:04:53
Message-ID: 20181209200453.szboteannavndez5@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2018-12-09 14:49:35 -0500, Tom Lane wrote:
> If the passed-in type OID isn't one of the very short list that
> TupleDescInitBuiltinEntry supports, it will silently hand back
> a broken TupleDesc, rather than throwing an error. How can
> this possibly be considered good code?

+1

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-12-09 20:42:57 Re: automatically assigning catalog toast oids
Previous Message Tom Lane 2018-12-09 19:49:35 Why does TupleDescInitBuiltinEntry lack a "default: error" case?