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 1lSLLk-0001IY-T1 for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Apr 2021 15:04:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lSLLj-00089m-RB for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Apr 2021 15:04:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lSLLj-00089f-Ka for pgsql-hackers@lists.postgresql.org; Fri, 02 Apr 2021 15:04:39 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lSLLh-00028r-AC for pgsql-hackers@lists.postgresql.org; Fri, 02 Apr 2021 15:04:39 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 8DA9C13C4; Fri, 2 Apr 2021 11:04:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 02 Apr 2021 11:04:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=wu2jY0VrCITMXHu2hpUzV1ARH05op8JmP9Dg/UpHXtU=; b=gwGHOkaE FZwjc2qSI0pMIEEq9KIZVk+Mgu7v4tO8eUxadFUxN2XOOR4RBcjzDs1AfWtFHAzm hyi905OcRPX/0aKbDhXxHsX018NYx0CgjPLepukZnFHZw5/XOBU1DeT6iehgNnSG G2SdjgUpp3gct5bClIGSxrbYqR1mUdKz2rBKm6FgMz4nD7xeBsHwf6vffLlAN/+g pU5Q8K5WcEts3wkIbyFlp2VkqlP4Y06EuDwDPbjkohF/RB5hQEaZb2evMNyAfAR+ lGKvx+Tn0GKn1M2szPVuZF6BbXuEZHNetOrPP8vJ0OGS6Rx69OGXrBbcmmI4BKR3 pbWuv64WoGoe3g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeiiedgkedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugfgjggfsehtke ertddtredunecuhfhrohhmpeetlhhvrghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhr vgesrghlvhhhrdhnohdqihhprdhorhhgqeenucggtffrrghtthgvrhhnpeeufffhjeeiue euffegvddukeegledtveeivdeiueefieeivefgteehueefteehvdenucfkphepudeltddr leehrdduledrleehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id 4FD95240068; Fri, 2 Apr 2021 11:04:33 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 150992A0850; Fri, 2 Apr 2021 12:04:31 -0300 (-03) Date: Fri, 2 Apr 2021 12:04:31 -0300 From: Alvaro Herrera To: Tom Lane Cc: Kyotaro Horiguchi , iwata.aya@fujitsu.com, tsunakawa.takay@fujitsu.com, k.jamison@fujitsu.com, pgsql-hackers@lists.postgresql.org Subject: Re: libpq debug log Message-ID: <20210402150431.GA14831@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3687898.1617375566@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Apr-02, Tom Lane wrote: > On third thought, maybe we should push your patch too. Although I think > 53aafdb9f is going to fix the platform-specific aspect of this, we are > still going to risk some implementation dependence of the libpq_pipeline > results: > > * Every so often, the number of digits in the reported line numbers > will change (999 -> 1001 or the like), due to changes in unrelated > code. Bah -- of course. > * Occasionally we refactor things so that the "same" error is reported > from a different file. True. (This was the reason for masking F and R, but I didn't realize that it'd have an effect in the message length). > It's hard to judge whether that will happen often enough to be an > annoying maintenance problem, but there's definitely a hazard. > Not sure if we should proactively lobotomize the test, or wait to > see if we get annoyed. I suspect we're going to see enough bf failures if we don't suppress it, because the problem is going to only show up with TAP testing enabled and the src/test/modules tests, which perhaps not all committers run. > In any case I'd like to wait till after drongo's next run, so > we can confirm whether or not the backslashes-in-__FILE__ hypothesis > is correct. If it is, then 53aafdb9f is a good fix on its own > merits, independently of libpq_pipeline. Wilco. -- Álvaro Herrera Valdivia, Chile Essentially, you're proposing Kevlar shoes as a solution for the problem that you want to walk around carrying a loaded gun aimed at your foot. (Tom Lane)