There’s xml data type in Postgres, I never used it before so I’d like to hear opinions. Downsides and upsides vs using regular varchar (or Text) column to store xml.
The text I’m going to store is xml, well-formed, UTF-8. No need to search by it (I’ve read searching by xml is slow).
This XML actually is data prepared for PDF generation with Apache FOP. XML can be generated dynamically from data found elsewhere (other Postgres tables), it’s stored as is only so that I won’t need to generate it twice. Kinda backup#2 for already generated PDF documents.
Anything else to know? Good practices, performance, maintenance, etc?
XMLdiffers fromTEXTonly logically: first, the input is checked for validity, second, theXMLtype lack comparison operators so you cannot index it, compare, use inUNIONorDISTINCTetc.If you are not going to search against it using indexes and want to make an extra check for validity, then use
XMLsafely.