From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bad optimizer data for xml (WAS: xml data type implications of no =) |
Date: | 2010-06-09 05:41:50 |
Message-ID: | 4C0F299E.7000803@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 09/06/10 17:14, Tom Lane wrote:
> Robert Haas<robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2010-06-09 06:58:59 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Sachin Srivastava | 2010-06-09 05:33:28 | Re: BUG #5475: Problem during Instalation |