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 1vrOAS-00135a-13 for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Feb 2026 22:31:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vrOAQ-000Oiy-12 for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Feb 2026 22:31:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vrOAP-000Oiq-2T for pgsql-hackers@lists.postgresql.org; Sat, 14 Feb 2026 22:31:09 +0000 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1vrOAH-00000000eWq-1lFW for pgsql-hackers@lists.postgresql.org; Sat, 14 Feb 2026 22:31:08 +0000 Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-59e6491f1a2so2193880e87.0 for ; Sat, 14 Feb 2026 14:31:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1771108259; cv=none; d=google.com; s=arc-20240605; b=RStHD9kgOo8bGRys93WC/aiJW2cpuLuSzRajToVTvSU6Ws6jEIoiE2mW8kPa9ONtld 4cCtTzZOeV7zUkS5m3LtrqbDMyZIhE0KVB1yaN1jYGMMpYhFWlQEHQ9JRX7YhKyqH3mp BRIty0xFxMoGzlZmpSEqhW3XM8Oeo10oUEXpqCLBenw8XD7DsgHHp08pXFSXtXR1sDUu 7HVwS4CTMH/jiwdrBMaJd7i3CT8HAKGoQX3FdPtqi7yst+Cs5HKLXNK4vlOi/Ysp/3rU o3qK20GGnGkcBX+JyHe2cBZL+vCtfZR8sqd52QYiJjRFs7Lzrvh1xOACyJJO7cmGMfaP EpSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=RGAKVK9KTdESSXAmbKaY+YKJcX/tCwQTovOTAV0jyx8=; fh=yYnkJjYocFSq23igNrRHLPwt/PhlwgGaQjMQ9la0r3A=; b=RKVerLvgoGkR1WOf9w147M/or5hw347nEHr/grgGfsU9tj7oDZvmGsu4NiMhuDwwyG 7/l4CEmJ0PdKSsMw7A5tW1skNWTdlwork7L8LJR0of+cLjkWzQuaaH9Zx94dZZP510Ll mYcdrd/B85L8dzEADohqm5ELcU8aZBVezBcP99cra2IE/RU16aIsv9FhIBAHczpYBQqL EuBgCmZPTCB/hRnIPObHz8e+Z0Ryoqux7TmJDp88XINt5GN5XMlR1M5qGEObSpxZdamO cc+jgHyl8INwHKg8hIN0gO1ZX+79/IaKs94SG90pBqoZgrbfDfsXPGNrYFB/vj2xWCKV vaSg==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1771108259; x=1771713059; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RGAKVK9KTdESSXAmbKaY+YKJcX/tCwQTovOTAV0jyx8=; b=QiFw/FyVNSSFQuW+WpvgJh1kPKVcSW+ncqxFKjVy7tcSOzvHcqAHN8ZeNJGfvZo2Aq N++/GTWyJ/foHdFmgVXhQnM3oUNdGXoanflMwOITD5x+MzCqxWi+aiitLJpnT4JPGd4e 0J5zjFJtrIAkjsrmlpRNhVDorvQKCNWaMdBL3wA9meprd1XtQXpxxjz9abiXXWmtlEr5 wdra0E/YhdCC2hFkeEbiZCcEkUMT5QrERD5qUiINCoYIVCZfJDeG33UWUfH+Nd6pXDxA wegYxxU3SyTjAf+eIrpkBVnURoKw4yRUhJpHIzLTngieUXOUMNQScGwGf3i7M7K2elhK OEMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771108259; x=1771713059; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=RGAKVK9KTdESSXAmbKaY+YKJcX/tCwQTovOTAV0jyx8=; b=UC0TYPM7olh9IlfUeIcSpkxdloDQ+PjhLAbgL2F1NRafdqtoxn0xfdf8ko6UWyUrQb w2kxidvodEcDntNzFfU5YjH8jeL+FNTSApyKPH13LMUkrQjxOh5K2MGAZfX1XwBpMr4M tXK/VDuclerDk30uBrKi0I3Mfy46Y6jspqFWwXCkqtOtqceObUldpt5hYyLaE0VTJVY/ ClssGT5w8qlAuOgw75af7o3jdJhcU3Pf5WtFolGHRQW9yCZgkWBPMAH8XDpHcb3e5T7N SuMR5rUZ5wKSyiNl4NNh5CY7Y5N5dvgTWQqMQ6IyGsefGYLhY1d/Oj/5x0GO2cDUpq7A GnzQ== X-Forwarded-Encrypted: i=1; AJvYcCVkJEGKq/tWPcIVR76774/kOjFi3ztHmMNIq3k59/I0djx6b5b4Oh+MRe6h/GULqwz+KhhVPVmH+Ln4YMzV@lists.postgresql.org X-Gm-Message-State: AOJu0YyuyPdezjGuuj6rKLP5EuByXDpe4vukIasIMCo+oGCQmTD5ovlH iG68qo7ulnmxWWpZz2fOu5GNpA7aUWZ6R6xMnJ6S+fwfxP5hodApsJ1tleauDgbnoADkHmB4uRx jIqv49g8Y2qmpHjLKTCdXZUkESqvmzPM= X-Gm-Gg: AZuq6aKeQ6GxvYnRvFC0vNDSNty1fAF/78zGWbGYj7b1dG50GIpyOj/WPvQJcVw/yE5 eppy8Sx2KE25a8P0+bPBiMTkZ923cfaIYgG8ITBl2JYSK3HN8sZaRYFIjkL1y8SE0Wn9ecD7mYQ qTHWJXx9uVF+FiYCQOiLBEaZqJN5izmAgKLsgw0YDCRU+Kpoi8FdyDkGOgS5vy+Sf4y4bcPr+z+ /eCbHdh98+MTA22xbJQgIp2jwqJLawFNxbx7SxQBIAdzST6lh0RINJQc8TH5SsEEGjt/0kEaf1V oQWY/XtTymvR/Ly91Vil0hZMS0aIyVerG8qWwO20 X-Received: by 2002:a05:6512:b10:b0:59e:4a2f:9911 with SMTP id 2adb3069b0e04-59f6cfe394amr1212319e87.23.1771108259190; Sat, 14 Feb 2026 14:30:59 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: From: Marcos Magueta Date: Sat, 14 Feb 2026 19:30:47 -0300 X-Gm-Features: AZwV_QgYTzC2HoeH970ci6DZ4c4j1jZLYivy0xWRtoR4BSxO74cCAwFlc0O1tFk Message-ID: Subject: Re: WIP - xmlvalidate implementation from TODO list To: Jim Jones Cc: Andrey Borodin , Kirill Reshke , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="000000000000a5db3b064ad0461c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a5db3b064ad0461c Content-Type: text/plain; charset="UTF-8" Hey Jim, I finally got back to it. > 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). I think you are right about removing the alias here, but I thought that on the previous exchange you were referring to the expression on x, not y. Nonetheless I see no point in keeping aliases here, however. I added it because I initially thought of aliasing chained expressions, but that makes little sense in an effectful command. > I'd suggest to focus on 0001 for now. Feel free to revert it to the > state of v4 if you disagree with the current approach. I am perfectly fine with the split, I think splitting it further will cause more problems to review because of their interdependency as you pointed out. It seems that for v6, all that is left is to revise the grant for read and write, and add the docs. Correct? If so, I will get started with it. Regards! --000000000000a5db3b064ad0461c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey=C2=A0Jim,

I finally got b= ack to it.

> On second thought, is there any scenario where we= 9;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).
I think you are right about removing the alias here, bu= t I thought that on the previous exchange you were referring to the=C2=A0ex= pression on x, not y. Nonetheless I see no point in keeping=C2=A0aliases he= re, however. I added it because I initially thought of aliasing chained exp= ressions, but that makes little sense in=C2=A0an effectful command.

=
>=C2=A0I'd suggest to focus on 0001 for now. Feel free to= revert it to the
> state of v4 if you disagree with the current appr= oach.
I am perfectly fine with the split, I think splitting i= t further will cause more problems to review because of their interdependen= cy as you pointed=C2=A0out.

It seems that for v6, all tha= t is left is to revise the grant for read and write, and add the docs. Corr= ect?

If so, I will get started with it.

Regards!
--000000000000a5db3b064ad0461c--