Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjJLb-00CkQj-1L for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Jan 2026 15:45:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vjJLa-000O5n-1s for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Jan 2026 15:45:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjJK4-000LPS-2q for pgsql-hackers@lists.postgresql.org; Fri, 23 Jan 2026 15:43:45 +0000 Received: from udcm-wwu2.uni-muenster.de ([128.176.118.28]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vjJK2-0000000068H-3xqN for pgsql-hackers@lists.postgresql.org; Fri, 23 Jan 2026 15:43:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-muenster.de; i=@uni-muenster.de; q=dns/txt; s=uniout; t=1769183023; x=1800719023; h=message-id:date:mime-version:subject:from:to:cc: references:in-reply-to:content-transfer-encoding; bh=uKRfz6Ti4lt1RflaC0hfNRtcoYONac4RRiu5ZQnl8pU=; b=GE6N1esy2Gm3bFvB/wZ0rJ4B/La6lVjCwH7eQ9CbPYy8eFt86n+VpkDs 7xP+1Hp7lny2McEBy3aDW6WNz3CGEPSHBjctzzreVYMbtMKVE+2Gph3wJ DOPtajYd8PeEqrrLahlQ72oXB1+9aR6I2sg5EphE5F3tKDVfweGnleyMe YIQeE56NweyHIqCzvdwlgwzP9PDVyOKh1owD192wiOAiAAR5RQu+gim/S E1YyE8ZwYfAZ3TzifZup1wTqnSncpcaNTu1JWP/b+F1dANs0sz20RGIEL dUvu2fiEjJ+szmKVq0Lh7YzQVm9fXkt0oyTNd+xj0a34i4FDBxGzeUe52 A==; X-CSE-ConnectionGUID: GQKxLm1kSTqlh1sllcYfsQ== X-CSE-MsgGUID: kVxkuqpKTOOR59HqhA6RZg== X-IronPort-AV: E=Sophos;i="6.21,248,1763420400"; d="scan'208";a="382281204" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 23 Jan 2026 16:43:41 +0100 Received: from [192.168.178.27] (dynamic-080-171-062-073.80.171.pool.telefonica.de [80.171.62.73]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id F00F520ADF00; Fri, 23 Jan 2026 16:43:40 +0100 (CET) Message-ID: Date: Fri, 23 Jan 2026 16:43:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: WIP - xmlvalidate implementation from TODO list From: Jim Jones To: Marcos Magueta Cc: Andrey Borodin , Kirill Reshke , PostgreSQL Hackers References: <89DE974B-F318-4D0A-A60B-51EDE84054E2@gmail.com> <9A074422-2308-4BD0-9FFA-0B6D70989935@yandex-team.ru> <70c72cb1-a39f-41b3-bfe3-e32ee7fda9c4@uni-muenster.de> <68a012d3-121b-418a-913b-aa0aaf32915d@uni-muenster.de> <2898f090-d9cf-475c-940c-a99da4a308f1@uni-muenster.de> <08052569-9384-41b5-bcb7-33929fcc6c71@uni-muenster.de> Content-Language: de-DE, en-GB In-Reply-To: <08052569-9384-41b5-bcb7-33929fcc6c71@uni-muenster.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 23/01/2026 13:19, Jim Jones wrote: > On 21/01/2026 21:44, Marcos Magueta wrote: >>> Any particular reason for that? If not, take a look at other options, >> e.g. a_expr >> No particular reason apart from it being simpler since I didn't need to >> invoke an execution at the cmd. Changed it now. On second thought, is there any scenario where we'll need a_expr for "y" at all in "CREATE XMLSCHEMA x AS y"? Isn't it always going to be a string? I see now that my example in the previous post was somewhat misleading (sorry for the noise). Best, Jim