Subject: Re: xPath in a database with LATIN1 encoding
To: Holger Jakobs <holger@jakobs.com>, pgsql-admin@lists.postgresql.org
References: <E8EDD295-7797-4EC7-9F60-96A9554CDEE6@gmail.com>
 <1707307.1619282961@sss.pgh.pa.us>
 <09A13721-516D-44B7-B8F9-5DC8A84BA62E@gmail.com>
 <caa976c4-6070-7eb8-1570-dee06b876a58@jakobs.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Message-ID: <8c308053-9d5d-0e06-1525-1c8baf269390@enterprisedb.com>
Date: Mon, 26 Apr 2021 12:19:03 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <caa976c4-6070-7eb8-1570-dee06b876a58@jakobs.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/8c308053-9d5d-0e06-1525-1c8baf269390%40enterprisedb.com>
Precedence: bulk

On 25.04.21 10:44, Holger Jakobs wrote:
> The point is that the XML standard dictates that every document without 
> an explicit encoding, must be encodied in UTF-8. So, whenever you want 
> to use a different encoding, this has to be stated in the XML header, as 
> indicated in Tom Lane's answer.

If you are transmitting an XML datum from the client to the server in 
the text protocol, then the encoding declaration is ignored.  See this 
documentation:

https://www.postgresql.org/docs/devel/datatype-xml.html#id-1.5.7.21.7