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 1hB3Si-0004Z9-2H for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Apr 2019 20:23:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hB3Sg-00005R-T4 for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Apr 2019 20:23:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hB3Sg-0008Ho-Dh for pgsql-hackers@lists.postgresql.org; Mon, 01 Apr 2019 20:23:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hB3Sd-0004f0-Si for pgsql-hackers@lists.postgresql.org; Mon, 01 Apr 2019 20:23:17 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x31KMVVt015146; Mon, 1 Apr 2019 16:22:31 -0400 From: Tom Lane To: Chapman Flack cc: Alvaro Herrera , Ryan Lambert , pgsql-hackers@lists.postgresql.org, Pavel Stehule Subject: Re: Fix XML handling with DOCTYPE In-reply-to: <5C9D5C94.4040408@anastigmatix.net> References: <20190327133152.GA7791@alvherre.pgsql> <5C9C023F.5070002@anastigmatix.net> <5C9C06DB.6090901@anastigmatix.net> <5C9D5C94.4040408@anastigmatix.net> Comments: In-reply-to Chapman Flack message dated "Thu, 28 Mar 2019 19:45:24 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15144.1554150151.1@sss.pgh.pa.us> Date: Mon, 01 Apr 2019 16:22:31 -0400 Message-ID: <15145.1554150151@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Chapman Flack writes: > So, xml-functions-type-docfix-6.patch. Pushed with some light(?) copy-editing. I believe this closes out everything discussed in https://commitfest.postgresql.org/22/1872/ but I haven't gone through all three threads in detail. Please confirm whether that CF entry can be closed or not. regards, tom lane