Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fW6ju-0007Iq-6U for pgsql-docs@arkaria.postgresql.org; Thu, 21 Jun 2018 21:03:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fW6js-0003F5-8Y for pgsql-docs@arkaria.postgresql.org; Thu, 21 Jun 2018 21:03:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fW6js-0003Ey-3I for pgsql-docs@lists.postgresql.org; Thu, 21 Jun 2018 21:03:32 +0000 Received: from mail-qt0-x244.google.com ([2607:f8b0:400d:c0d::244]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fW6jo-0003GN-73 for pgsql-docs@postgresql.org; Thu, 21 Jun 2018 21:03:31 +0000 Received: by mail-qt0-x244.google.com with SMTP id q6-v6so4181189qtn.7 for ; Thu, 21 Jun 2018 14:03:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=08XD4MKsgB0RaKuAWN7VVPjGvUgkp3ylq4/LDUXOvbc=; b=hFCZiUzYqAjG+aQmooyvSS2mlmiHyptQBo0f0jjxMdpiXBaXEU+ysOVV9bcWRuutng GiAoZ+OGPwVp5kSo7qZ29AEJvWtH0BDdHMgvnnNTtAJlAO/fpRtg03b/Vucgggfot7Xi EfRMWnykz0Ir2pSLtA8NnDd+cp9Xu87Iu9+fG9OAVlNlR9PDfZagQe6Lc4dr5pAydOJ9 AtOXurMdvClLgdUXqoOOK63E8C3coA8iQqBOPYSMzCRJb24wqpV3/Az4r3e3hMMzrgyO eZockFPwnxay/To5+RZRGQmX7KLA7uuunTp/tUnsugRtgqGHCFXDzkE1vYDLlDcSfHaV +reQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=08XD4MKsgB0RaKuAWN7VVPjGvUgkp3ylq4/LDUXOvbc=; b=KWlKA5v9wFT0Z4Ka2AVJYV6LqmgSYT2W0dWPsUEzE9j44h60CFdleR7nCnX0M6ok1r u+T8eaPnBLnwYZs4ljmLAly1tiznneN3cV3aBowtcsbTX/wD+0lNXaO4uqfM7hdmDNYb ayJHo3+q+QSS8WVpyz7AVYGmBexZ3KcKefAM1n5oBuj9GWiY70B1Kr0qpKvVfTnFzy7j Xuv1Pr/8W3iVaa0sHDZbvGj1i2kpvzuyx4tbIBOK7U35EssuWpGRYbwT7BnO/AQTjMY+ 3OOwwAHHp4PgOeeoR9+hF4uNG9xqvC4Qq50k7nYjuj5TRscQqyoGx+Y+KdY79/fd6uV3 +dtg== X-Gm-Message-State: APt69E3+6fIMqVmpwtgVZ4AKikk4ihiHCTRBkVCm9fgw/n7XRqxmUXK1 J3yYXTeM3pWLvSO2o/fGqqqBGA== X-Google-Smtp-Source: ADUXVKLfsf1zJE8btM5kpzWWCMoBHT6tMz4FJei0TJMRPoGpIjvBa4imVum8YpGlJ/Ly69FihVYd3A== X-Received: by 2002:ac8:2191:: with SMTP id 17-v6mr25172874qty.279.1529615005090; Thu, 21 Jun 2018 14:03:25 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id t4-v6sm4880854qki.48.2018.06.21.14.03.24 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Jun 2018 14:03:24 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 6CD6B600; Thu, 21 Jun 2018 17:03:22 -0400 (-04) Date: Thu, 21 Jun 2018 17:03:22 -0400 From: Alvaro Herrera To: Daniel Gustafsson Cc: pgsql-docs , Pavel Stehule Subject: Re: [DOCS] XMLTABLE default namespace in docs Message-ID: <20180621210322.c4a5jiaiouqsblix@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1550C5E5-FC70-4493-A226-AA137D831E8D@yesql.se> User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2017-Sep-11, Daniel Gustafsson wrote: > When reviewing Pavels patch for default namespace in XMLTABLE, I came across > this sentence in the devel (and 10beta) docs in subsection 9.14.3.3. xmltable: > > The following example illustrates how the XMLNAMESPACES clause can be > used to specify the default namespace, and a list of additional > namespaces used in the XML document as well as in the XPath > expressions: > > That seems odd since we don’t support default namespaces (hence the patch for > adding it). Am I reading it wrong, or shouldn’t we apply something like the > attached for now? You're right, we should -- thanks for noticing. I have pushed it now. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services