Re: amvalidate(): cache lookup failed for operator class 123
| От | Tom Lane |
|---|---|
| Тема | Re: amvalidate(): cache lookup failed for operator class 123 |
| Дата | |
| Msg-id | 1639993.1620938986@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: amvalidate(): cache lookup failed for operator class 123 (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: amvalidate(): cache lookup failed for operator class 123
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, May 13, 2021 at 2:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Meh. I'm not convinced that that position ought to apply to amvalidate.
> I am still of the opinion that we ought to apply it across the board,
> for consistency.
The main reason I'm concerned about applying that rule to amvalidate
is that then how do you know what's actually an error case?
As a hardly-irrelevant counterexample, we have a whole bunch of
regression tests that do something like
SELECT ...
WHERE NOT amvalidate(oid);
Every one of those is silently and dangerously wrong if amvalidate
might sometimes return null.
regards, tom lane
В списке pgsql-hackers по дате отправления: