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 AANLkTikXDv-OkulgAg8vegjMFiced3rgdHFUXSoNyKfD@mail.gmail.com
Whole thread Raw
In response to Re: Bad optimizer data for xml (WAS: xml data type implications of no =)  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Responses Re: Bad optimizer data for xml (WAS: xml data type implications of no =)  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Re: Bad optimizer data for xml (WAS: xml data type implications of no =)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, Jun 3, 2010 at 7:16 PM, Mark Kirkwood
<mark.kirkwood@catalyst.net.nz> wrote:
> Maybe I gave this guy a bad title - is it a concern that the 'width'
> estimate is so far off for xml datatypes (because of no = op)? It seemed to
> me that this could result in some bad plan choices (e.g in subqueries etc).

It's possible.  I don't really see a reason not to add an = operator
for XML - does anyone else?

It would need to be done by updating src/include/catalog/pg_*.h,
rather than via SQL, of course.

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

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: [BUGS] Reinicialização - Pg_Listener
Next
From: Mark Kirkwood
Date:
Subject: Re: Bad optimizer data for xml (WAS: xml data type implications of no =)