Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pSEln-00084q-RR for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Feb 2023 10:12:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pSElm-0005iu-GP for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Feb 2023 10:12:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pSEll-0005g2-PM for pgsql-hackers@lists.postgresql.org; Wed, 15 Feb 2023 10:12:10 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pSElg-0000kW-Sj for pgsql-hackers@lists.postgresql.org; Wed, 15 Feb 2023 10:12:08 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D46E55C004B; Wed, 15 Feb 2023 05:12:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 15 Feb 2023 05:12:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1676455922; x=1676542322; bh=7 NDITezcxh8B6bLFTCv9ak0/H1JaPAyWOMH22ytM08w=; b=KY6vUOfsUyCxvgIYc lgfgio4o0A1AJW10mUSPg5AbfevyvwjRfMlfEApI6KGOr3Z5vUxe4L92caCWP2dh I9f0Z/zFlObgWwgpnsUhq5TbVY2sz10RROBpG3PhJgv6tZnqW7dRTBuYa3DQXbjd 8LE4S2zf5y2e2KhD+CFC6ZFtnmgZyZTN6jnGajL4KpOpYiA7QVTwOrgDM551KCFf pgHTy1Fd3TvXGeQ+P5C3VA8e8JYiCpqHQkOQ6NYVD520qh0mbcQ5MQV3CurhaNpl vd9Oq/3ftpkD3vITQhg+Y0/t2ZTKzI8MeX+qCSoCb5LPwAmmMWLD1v5BMvasffuR xLjuw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeihedgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 Feb 2023 05:12:01 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 778609E; Wed, 15 Feb 2023 11:11:59 +0100 (CET) Date: Wed, 15 Feb 2023 11:11:59 +0100 From: Alvaro Herrera To: Peter Smith Cc: Jim Jones , Tom Lane , pgsql-hackers@lists.postgresql.org, Peter Eisentraut Subject: Re: [PATCH] Add pretty-printed XML output option Message-ID: <20230215101159.ef5usgukz2qfgp5n@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Feb-13, Peter Smith wrote: > Something is misbehaving. > > Using the latest HEAD, and before applying the v6 patch, 'make check' > is working OK. > > But after applying the v6 patch, some XML regression tests are failing > because the DETAIL part of the message indicating the wrong syntax > position is not getting displayed. Not only for your new tests -- but > for other XML tests too. Note that there's another file, xml_2.out, which does not contain the additional part of the DETAIL message. I suspect in Peter's case it's xml_2.out that was originally being used as a comparison basis (not xml.out), but that one is not getting patched, and ultimately the diff is reported for him against xml.out because none of them matches. An easy way forward might be to manually apply the patch from xml.out to xml_2.out, and edit it by hand to remove the additional lines. See commit 085423e3e326 for a bit of background. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/