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 1nhttN-0008Ui-A1 for pgsql-committers@arkaria.postgresql.org; Fri, 22 Apr 2022 14:04:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nhttM-0007uA-4j for pgsql-committers@arkaria.postgresql.org; Fri, 22 Apr 2022 14:04:12 +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 1nhttL-0007q0-TY for pgsql-committers@lists.postgresql.org; Fri, 22 Apr 2022 14:04:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nhttI-0006oa-1f; Fri, 22 Apr 2022 14:04:10 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 23ME45313687649; Fri, 22 Apr 2022 10:04:05 -0400 From: Tom Lane To: Andrew Dunstan cc: Robert Haas , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Allow db.schema.table patterns, but complain about random garbag In-reply-to: <3a190754-b2b0-d02b-dcfd-4ec1610ffbcb@dunslane.net> References: <3a190754-b2b0-d02b-dcfd-4ec1610ffbcb@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Fri, 22 Apr 2022 09:15:31 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3687647.1650636245.1@sss.pgh.pa.us> Date: Fri, 22 Apr 2022 10:04:05 -0400 Message-ID: <3687648.1650636245@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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. regards, tom lane