Thread
Commits
-
Make TupleDescInitBuiltinEntry throw error for unsupported types.
- a628e0c5b484 11.2 landed
- 9eaba23c414d 10.7 landed
- b7a29695f744 12.0 landed
-
Why does TupleDescInitBuiltinEntry lack a "default: error" case?
Tom Lane <tgl@sss.pgh.pa.us> — 2018-12-09T19:49:35Z
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? (So far as I can see, none of the extant callers could hit such an error, but it's still bad code.) regards, tom lane
-
Re: Why does TupleDescInitBuiltinEntry lack a "default: error" case?
Andres Freund <andres@anarazel.de> — 2018-12-09T20:04:53Z
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