| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrey Borodin <amborodin86(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Add pretty-printed XML output option |
| Date: | 2023-03-10 14:32:56 |
| Message-ID: | 803304.1678458776@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> writes:
> On 09.03.23 21:21, Tom Lane wrote:
>> I've looked through this now, and have some minor complaints and a major
>> one. The major one is that it doesn't work for XML that doesn't satisfy
>> IS DOCUMENT. For example,
> How do you suggest the output should look like?
I'd say a series of node trees, each starting on a separate line.
>> I also suspect that it's outright broken to attach a header claiming
>> the data is now in UTF8 encoding. If the database encoding isn't
>> UTF8, then either that's a lie or we now have an encoding violation.
> I was mistakenly calling xml_parse with GetDatabaseEncoding(). It now
> uses the encoding of the given doc and UTF8 if not provided.
Mmmm .... doing this differently from what we do elsewhere does not
sound like the right path forward. The input *is* (or had better be)
in the database encoding.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-03-10 14:38:17 | Re: pgsql: Use ICU by default at initdb time. |
| Previous Message | Masahiko Sawada | 2023-03-10 14:30:04 | Re: [PoC] Improve dead tuple storage for lazy vacuum |