Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ibieW-0005cW-VR for pgsql-committers@arkaria.postgresql.org; Mon, 02 Dec 2019 10:10:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ibieV-0006e5-NF for pgsql-committers@arkaria.postgresql.org; Mon, 02 Dec 2019 10:09:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ibieU-0006dy-MZ for pgsql-committers@lists.postgresql.org; Mon, 02 Dec 2019 10:09:59 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ibieQ-0001Rw-KY for pgsql-committers@lists.postgresql.org; Mon, 02 Dec 2019 10:09:57 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 1A996978; Mon, 2 Dec 2019 05:09:52 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 02 Dec 2019 05:09:53 -0500 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:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=MT5qjco9cNDhhjYaOAP0Q2W29877EdPBxViQmTmWU 4M=; b=X84K6rqNn6KBf9QRoDTYBW8qZJjrdwVVrhYuQLgFW7Rl13B/bsGbMWUpj sd56Y9yD8wVnpWhyzklQ3OWN/EBeTfkNKHY5JQNa5vu/b71RBzTfo79cHopqOmkV p6WVLzKKxSdFIYVDWpTiymFPJnyVsBeIjnDukdcpjxFj0V2iKbzInCShCe6oANWI JDT8jLaFaeAU+/1awV7HmsGm8msogUY8YZJVgWwgCp3qHgzQnMbPFEyv9E7a7aET DtDACYBVu1J3Mrp0qu6ZHw58PWaHA7cxqPkdJt0fq5Cgvsr+wylcoQqX/keVBRFH n34tJ+0RFGEseQWw9Sz7YSdiqeUdw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejhedgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhfhokffffgggjggtgfesth ejredttdefjeenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgv rhdrvghishgvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhmqeenucffohhmrg hinhepvdhnughquhgrughrrghnthdrtghomhenucfkphepleefrddvgedvrddugeejrdej leenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhhtse dvnhguqhhurggurhgrnhhtrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from april.pezone.net (p5df2934f.dip0.t-ipconnect.de [93.242.147.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 7BE6D80061; Mon, 2 Dec 2019 05:09:51 -0500 (EST) Subject: Re: pgsql: Add a regression test for allow_system_table_mods To: Tom Lane References: <13656.1575041267@sss.pgh.pa.us> <315cfd3b-9d04-0ea4-76d8-1507c8bd9bb7@2ndquadrant.com> <15399.1575043746@sss.pgh.pa.us> Cc: pgsql-committers@lists.postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <1e7bb9a1-1104-907d-da62-857408d271ef@2ndquadrant.com> Date: Mon, 2 Dec 2019 11:09:49 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <15399.1575043746@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-11-29 17:09, Tom Lane wrote: >>> +WARNING: tablespaces created by regression test cases should have names starting with "regress_" > I agree that this is somewhat pointless in the case of an "unsafe" test. > But using a different name isn't going to invalidate the test case, > so there's not really a reason to not follow the convention. And > trying to have an exception for unsafe_tests seems like a lot more > trouble than it'd be worth. The test case is specifically testing tablespace names starting with "pg_": -- reserved tablespace name CREATE TABLESPACE pg_foo LOCATION '/no/such/location'; ERROR: unacceptable tablespace name "pg_foo" DETAIL: The prefix "pg_" is reserved for system tablespaces. So using a name starting with "regress_" instead isn't going to help. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services