Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lb2VF-0004zF-7t for pgsql-admin@arkaria.postgresql.org; Mon, 26 Apr 2021 14:46:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lb2VE-0003Pp-52 for pgsql-admin@arkaria.postgresql.org; Mon, 26 Apr 2021 14:46:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lb1X8-00029U-Mw for pgsql-admin@lists.postgresql.org; Mon, 26 Apr 2021 13:44:18 +0000 Received: from forward3-smtp.messagingengine.com ([66.111.4.237]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lb1X6-0000wq-4x for pgsql-admin@lists.postgresql.org; Mon, 26 Apr 2021 13:44:17 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id F005C1940B9E; Mon, 26 Apr 2021 09:44:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 26 Apr 2021 09:44:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=YmP/vvWTLZC3QFcQwpXHTYd3mV1Eaa1avaDdB042p lY=; b=N6ZQF+qWtyuPBFgU0wuJWT+OUGXMKK97hTg7nNcY4hjlefYGXXae0dpgq 328DysoN0gLgj+48Zt40JlfHrDokWREVkG3yGtTgosC4iS5JDHpaqLjE7ILY41f/ K/ahkXIGEmsjv77o5Szn0zjym71i3Py+yTOdPW3WYP00rs3NtfFtNONE79cCbISQ KcDIDrTt9IFIM76rwQ5Y6okAuaWFA7hG/tEU6CssjAKQQDcMxgPlVo405L6J5iyn CrrGsj2lbURdck8W2DJx3XVcNJ1IKZsgSDRq2ApoBxoGo9JTrhUS4F3LBO//35w7 wZ6Zuws9OSF/VV5CHqChtpK39wIIA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddukedgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvg hrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheetjeeffeelffdtfeeg vdeijeehtdeutdelieeljeehledtvdevvddugeevfeetnecuffhomhgrihhnpehpohhsth hgrhgvshhqlhdrohhrghenucfkphepledurddugedrvddvgedruddvtdenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvg hnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: from laptop206oxuk.local (p5b0ee078.dip0.t-ipconnect.de [91.14.224.120]) by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 26 Apr 2021 09:44:12 -0400 (EDT) Subject: Re: xPath in a database with LATIN1 encoding To: Jorge Silva , Pgsql-admin References: From: Peter Eisentraut Message-ID: Date: Mon, 26 Apr 2021 15:44:11 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 24.04.21 17:20, Jorge Silva wrote: > We have a database, which is encoded with LATIN1, and we are adding some > tables in it to store xml files with the “xml” type. After creating the > table and populating it, we use the xPath function to retrieve some data > from the XML, but it seems to not work properly, because it returns: As documented at , xpath only works if the server encoding is UTF8.