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 1n83TZ-00065H-JL for pgsql-committers@arkaria.postgresql.org; Thu, 13 Jan 2022 17:01:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n83TY-0003Re-Do for pgsql-committers@arkaria.postgresql.org; Thu, 13 Jan 2022 17:01:24 +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 1n83TY-0003Qt-6y for pgsql-committers@lists.postgresql.org; Thu, 13 Jan 2022 17:01:24 +0000 Received: from relay10.mail.gandi.net ([2001:4b98:dc4:8::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n83TR-00060S-F9 for pgsql-committers@lists.postgresql.org; Thu, 13 Jan 2022 17:01:23 +0000 Received: (Authenticated sender: adsend@dunslane.net) by relay10.mail.gandi.net (Postfix) with ESMTPSA id 6F41324000D; Thu, 13 Jan 2022 17:01:10 +0000 (UTC) Message-ID: <5ff5239e-b5b2-6874-9667-e927ec55f1db@dunslane.net> Date: Thu, 13 Jan 2022 12:01:08 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: pgsql: Check for STATUS_DELETE_PENDING on Windows. Content-Language: en-US To: Tom Lane Cc: Thomas Munro , Thomas Munro , pgsql-committers References: <2760528.1641929756@sss.pgh.pa.us> <8320cca6-5647-be5d-9b22-914415bcbc27@dunslane.net> <2801180.1641938050@sss.pgh.pa.us> From: Andrew Dunstan In-Reply-To: <2801180.1641938050@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 1/11/22 16:54, Tom Lane wrote: > Andrew Dunstan writes: >> On 1/11/22 16:22, Thomas Munro wrote: >>> Those scripts aren't really on my radar... would it be a good idea to >>> run them as steps in the CompilerWarnings CI task? >> Or in a buildfarm module (c.f. the perl checks) > +1 for one or the other, because we break that regularly and it > typically takes awhile to notice. > > Done See crake will now run this as part of its normal runs on HEAD. cheers andew -- Andrew Dunstan EDB: https://www.enterprisedb.com