| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Anton <antonin(dot)houska(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Native XML |
| Date: | 2011-03-10 00:03:04 |
| Message-ID: | 4D781538.5020500@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/9/11 10:11 AM, Bruce Momjian wrote:
> If you are storing xml in an xml column just to get it
>> validated, and doing no processing in the DB, then you'd probably
>> prefer our current representation. If you want to build functional
>> indexes on xpath expressions, and then run queries that extract data
>> using other xpath expressions, you would probably prefer the other
>> representation.
Then I think the answer is that we need both data types. One for
text-XML and one for binary-XML.
For my part, I don't use PostgreSQL's native XML tools for storage of
XML data because the xpath functions are too slow and limited to make PG
useful as an XML database.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2011-03-10 00:05:19 | Re: Fwd: psql include file using relative path |
| Previous Message | Nikhil Sontakke | 2011-03-09 23:28:19 | Re: Fwd: index corruption in PG 8.3.13 |