Re: Bad optimizer data for xml (WAS: xml data type implications of no =)

Поиск
Список
Период
Сортировка
От Mark Kirkwood
Тема Re: Bad optimizer data for xml (WAS: xml data type implications of no =)
Дата
Msg-id 4C0F299E.7000803@catalyst.net.nz
обсуждение исходный текст
Ответ на Re: Bad optimizer data for xml (WAS: xml data type implications of no =)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Bad optimizer data for xml (WAS: xml data type implications of no =)
Список pgsql-bugs
On 09/06/10 17:14, Tom Lane wrote:
> Robert Haas<robertmhaas@gmail.com>  writes:
>
>> It's possible.  I don't really see a reason not to add an = operator
>> for XML - does anyone else?
>>
> Yes, that was considered and rejected, IIRC.  What is your definition
> of equality for xml?
>

Yes - but in that previous discussion the optimizer (lack of)
information was not considered (or known I suspect), so maybe a rethink
is worthwhile?

It seems that the nub of this issue is that there are conceptually two
types of =, one for datatype specific comparison, and one for optimizer
statistical information calculation. However the system allows only the
first, so if you don't (or can't) have one then you lose some possibly
important optimization data.

regards

Mark

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

Предыдущее
От: Sachin Srivastava
Дата:
Сообщение: Re: BUG #5475: Problem during Instalation
Следующее
От: Dean Rasheed
Дата:
Сообщение: Re: Invalid YAML output from EXPLAIN