Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h7p0f-0004f3-Q4 for pgsql-hackers@arkaria.postgresql.org; Sat, 23 Mar 2019 22:21:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h7p0d-0005wX-Rz for pgsql-hackers@arkaria.postgresql.org; Sat, 23 Mar 2019 22:20:59 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1h7p0d-0005vu-Ki for pgsql-hackers@lists.postgresql.org; Sat, 23 Mar 2019 22:20:59 +0000 Received: from anastigmatix.net ([68.171.219.55]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h7p0b-0003hF-2h for pgsql-hackers@lists.postgresql.org; Sat, 23 Mar 2019 22:20:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=n2vayzDI+F7VJyJ5aHTpNjf9oyBemfZhjApJRM+W/5E=; b=KjUV0ncteQ5zkgBIq/2fIhRsfg h0PzMceYgDNipgz+7y08iashP06LxEsms4uwL3QfatcZdZ0f+yC9y1k8VDv/c0NuU6O+qO8+25jtX 0Q1HGdD6L86yk12QSEZztY9EBNs8kKaEYIJpUvx3Ib4QG6gXyfBlY3lxRK/4xPbsWBLg2odm+hSL8 17zEjefUffe5+ECRvTNHKigTRBLhim2bZLf1hMVnNa/f+wMMKJcDoM1tztHwSkkCnJM+2+qecNsKE nHdPwTzbA2jt00yV8KNqnXPfPxoRSx9HxgtF/5xNZfTnaGd5bYNViWfXtzVaN9SvexCTw8jtdNGFe bkOU3CHw==; Received: from [184.19.63.78] (port=50122) by bay.acenet.us with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1h7p0U-00C2n2-Jp; Sat, 23 Mar 2019 18:20:54 -0400 Subject: Re: The two "XML Fixes" patches still in need of review To: Tom Lane References: <5C81F8C0.6090901@anastigmatix.net> <12427.1553375114@sss.pgh.pa.us> Cc: PostgreSQL Hackers , Markus Winand , Alvaro Herrera , Michael Paquier , Pavel Stehule From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <5C96B141.5050802@anastigmatix.net> Date: Sat, 23 Mar 2019 18:20:49 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <12427.1553375114@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-95.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 03/23/19 17:05, Tom Lane wrote: > Just to update this thread --- per the other thread at > https://postgr.es/m/CAN-V+g-6JqUQEQZ55Q3toXEN6d5Ez5uvzL4VR+8KtvJKj31taw@mail.gmail.com > I've now pushed a somewhat-adjusted version of the XML-content fix > patch. The documentation patch needs some small rebasing to apply > after that one instead of before it. Will do. > Perhaps it'd make sense under the XML section in datatype.sgml, > but I think I might lean to making it a new section in Appendix D > (SQL Conformance). Sounds like the option (4) I proposed back in [1]. I suppose it won't be much trouble to move. > I'm not going to touch the documentation patch myself; I don't know > enough about XML to review it competently. I would be happy even to see it reviewed for style, and if anybody's willing to look at the technical content even if not feeling ideally prepared, I'd be happy to respond or give references for any points in question. It does fix a number of actual bugs in the existing documentation, so while it would be ideal to apply a higher standard of technical review to this patch, it'd be less ideal to have existing buggy doc lingering on because nobody feels up to reviewing at that ideal higher standard. Regards, -Chap [1] https://www.postgresql.org/message-id/5C298BCB.4060704%40anastigmatix.net