contrib/xml2 has been claimed to be deprecated since PostgreSQL 8.3. I took a look through the functions it offers and perhaps with xmltable now being available, they could all be replaced using built-in functions, perhaps with some small tweaking.
But we don't have any replacement lined up for the XSLT processing function xslt_process. What should we do with that, assuming that we eventually want to remove contrib/xml2 altogether? 1. Just remove it, leaving users to find other solutions. (PL/P* can probably fill the gap.) 2. Create a new extension contrib/xslt, move the implementation there. (Optionally, have contrib/xml2 depend on this new extension if it is not ready to be removed.) 3. Add XSLT functionality to core (unlikely). Thoughts? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
