PostgreSQL does not have a specialized XML data type. Users should store XML documents in ordinary TEXT fields. If you need the document split apart into its component parts so each element is stored separately, you must use a middle-ware solution to do that, but once done, the data becomes relational and has to be processed accordingly.

There is no facility for mapping XML to relational tables. An external tool must be used for this. One simple way to export XML is to use psql in HTML mode (\pset format html), and convert the XHTML output to XML using an external tool.

/contrib/xml2 has a function called xml_is_well_formed() that can be used in a CHECK constraint to enforce that a field contains well-formed XML. It does not support validation against a specific XML schema. A server-side language with XML capabilities could be used to do schema-specific XML checks.

/contrib/xml2 functions can be used in expression indexes to index specific XML fields. To index the full contents of XML documents, the full-text indexing tool /contrib/tsearch2 can be used. Of course, Tsearch2 indexes have no XML awareness so additional /contrib/xml2 checks should be added to queries.

If an UPDATE does not modify an XML field, the XML data is shared between the old and new rows. However, if the UPDATE modifies an XML field, a full modified copy of the XML field must be created internally.

XPath searches are implemented using /contrib/xml2. It processes XML text documents and returns results based on the requested query.

/contrib/xml2 supports XSLT (Extensible Stylesheet Language Transformation).

This involves converting XML data to and from relational structures. PostgreSQL has no internal support for such mapping, and relies on external tools to do such conversions.

Missing features include XQuery, SQL/XML syntax (ISO/IEC 9075-14), and an XML data type optimized for XML storage.