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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Why does TupleDescInitBuiltinEntry lack a "default: error" case?
Дата
Msg-id 30830.1544384975@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: Why does TupleDescInitBuiltinEntry lack a "default: error" case?  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alexander Korotkov
Дата:
Сообщение: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Why does TupleDescInitBuiltinEntry lack a "default: error" case?