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 1oHYKn-0007tI-Sz for pgsql-committers@arkaria.postgresql.org; Fri, 29 Jul 2022 22:19:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oHYKj-0008NE-Km for pgsql-committers@arkaria.postgresql.org; Fri, 29 Jul 2022 22:19:49 +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 1oHYKj-0008Mw-Dp for pgsql-committers@lists.postgresql.org; Fri, 29 Jul 2022 22:19:49 +0000 Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHYKf-00033T-Dk for pgsql-committers@lists.postgresql.org; Fri, 29 Jul 2022 22:19:48 +0000 Received: (Authenticated sender: adsend@dunslane.net) by mail.gandi.net (Postfix) with ESMTPSA id 88A5AC0002; Fri, 29 Jul 2022 22:19:40 +0000 (UTC) Message-ID: Date: Fri, 29 Jul 2022 18:19:38 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: pgsql: Fix new recovery test for log_error_verbosity=verbose case Content-Language: en-US To: Tom Lane Cc: pgsql-committers@lists.postgresql.org References: <45978.1659132532@sss.pgh.pa.us> From: Andrew Dunstan In-Reply-To: <45978.1659132532@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-07-29 Fr 18:08, Tom Lane wrote: > Andrew Dunstan writes: >> Fix new recovery test for log_error_verbosity=verbose case >> The new test is from commit 9e4f914b5e. >> With this setting messages have SQL error numbers included, so that >> needs to be provided for in the pattern looked for. > That needs to be back-patched, no? > > Oops, yes, for some reason my update script failed. That's done now. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com