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 1nhuD7-00016A-C9 for pgsql-committers@arkaria.postgresql.org; Fri, 22 Apr 2022 14:24:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nhuD6-0004vV-0B for pgsql-committers@arkaria.postgresql.org; Fri, 22 Apr 2022 14:24:36 +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 1nhuD5-0004vH-P1 for pgsql-committers@lists.postgresql.org; Fri, 22 Apr 2022 14:24:35 +0000 Received: from relay6-d.mail.gandi.net ([2001:4b98:dc4:8::226]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nhuD3-0000lO-Dv for pgsql-committers@lists.postgresql.org; Fri, 22 Apr 2022 14:24:35 +0000 Received: (Authenticated sender: adsend@dunslane.net) by mail.gandi.net (Postfix) with ESMTPSA id 213F4C0006; Fri, 22 Apr 2022 14:24:28 +0000 (UTC) Message-ID: Date: Fri, 22 Apr 2022 10:24:27 -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: Allow db.schema.table patterns, but complain about random garbag Content-Language: en-US To: Tom Lane Cc: Robert Haas , pgsql-committers@lists.postgresql.org References: <3a190754-b2b0-d02b-dcfd-4ec1610ffbcb@dunslane.net> <3687648.1650636245@sss.pgh.pa.us> From: Andrew Dunstan In-Reply-To: <3687648.1650636245@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-04-22 Fr 10:04, Tom Lane wrote: > Andrew Dunstan writes: >> This has upset the buildfarm's msys2 animals. There appears to be some >> wildcard expansion going on that causes the problem. I don't know why it >> should here when it's not causing trouble elsewhere. I have tried >> changing the way the tests are quoted, without success. Likewise, >> setting SHELLOPTS=noglob didn't work. >> At this stage I'm fresh out of ideas to fix it. It's also quite possible >> that my diagnosis is wrong. > When I was looking at this patch, I thought the number of test cases > was very substantially out of line anyway. I suggest that rather > than investing a bunch of brain cells trying to work around this, > we just remove the failing test cases. WFM. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com