Re: Bad optimizer data for xml (WAS: xml data type implications of no =) - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Bad optimizer data for xml (WAS: xml data type implications of no =)
Date
Msg-id AANLkTikKCRt6sGM6lpJFr-TvhTJeGpOQYbcUx6nbbPPg@mail.gmail.com
Whole thread Raw
In response to Re: Bad optimizer data for xml (WAS: xml data type implications of no =)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bad optimizer data for xml (WAS: xml data type implications of no =)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Wed, Jun 9, 2010 at 1:14 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> It's possible. =A0I don't really see a reason not to add an =3D operator
>> for XML - does anyone else?
>
> Yes, that was considered and rejected, IIRC. =A0What is your definition
> of equality for xml?

I'd vote for !memcmp().

There can be (and probably already are) other ways to test for other
kinds of equality, too, of course.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5475: Problem during Instalation
Next
From: Robert Haas
Date:
Subject: Re: BUG #5475: Problem during Instalation