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 1h5Fxt-0007xz-4D for pgsql-hackers@arkaria.postgresql.org; Sat, 16 Mar 2019 20:31:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h5Fxq-0002PI-O9 for pgsql-hackers@arkaria.postgresql.org; Sat, 16 Mar 2019 20:31:30 +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 1h5Fxq-0002PB-2L for pgsql-hackers@lists.postgresql.org; Sat, 16 Mar 2019 20:31:30 +0000 Received: from anastigmatix.net ([68.171.219.55]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h5Fxj-0005uL-8j for pgsql-hackers@postgresql.org; Sat, 16 Mar 2019 20:31:28 +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:References:To:Subject:Sender: Reply-To:Cc: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=6wTwATj2JOXuXgUJye+SAuCBgklC1hhEjoh7xmx1LZE=; b=HSM48FrqlMN/jwO1BmyRtWJjC0 N1bDHsxA+NXiUdQ+pvEq7bR+wdB8ugm9jmlNxWhjRDRwcmq5uBpqLO5MbUuCRJ18w2116zhAQvG8v Uds/SoUQIYYqw966o9MYlO9Z6BYQtITHn57ZVUi+7JabH43zgqQsKUAPXwhARfNNcUB6dHwdW0PcO lXJPSfnVy4+SKrRfpoLzMeckYhiP1+/iBtNdSpk+NGTO5duEdw2NrCBWw5ewXIWDFcspWw84Lftov dCf9QMxtAvBt14SgLUsW8pTnZ+g04PSHAEG8vIAw7zKuZojfAFkl61aZc7tm4bp60AHfk0wNqFtyL GoH6KueA==; Received: from [184.19.63.78] (port=45590) by bay.acenet.us with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1h5Fxf-00FTqB-Hb; Sat, 16 Mar 2019 16:31:20 -0400 Subject: Re: Fix XML handling with DOCTYPE To: Ryan Lambert , pgsql-hackers@postgresql.org References: From: Chapman Flack Message-ID: <5C8D5D16.7090206@anastigmatix.net> Date: Sat, 16 Mar 2019 16:31:18 -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: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-98.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 - 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/16/19 16:10, Ryan Lambert wrote: > As Tom Lane mentioned there, the docs (8.13) indicate xmloption = CONTENT > should accept all valid XML. At this time, XML with a DOCTYPE declaration > is not accepted with this setting even though it is considered valid XML. Hello Ryan, A patch for your issue is currently registered in the 2019-03 commitfest[1]. If it attracts somebody to review it before the end of the month, it might make it into PG v12. It is the xml-content-2006-2.patch found on the email thread [2]. (The other patch found there is associated documentation fixes, and also needs to be reviewed.) Further conversation should probably be on that email thread so that it stays associated with the commitfest entry. Thanks for your interest in the issue! Regards, Chapman Flack [1] https://commitfest.postgresql.org/22/1872/ [2] https://www.postgresql.org/message-id/flat/5C81F8C0.6090901@anastigmatix.net