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 1pJiKK-0002zK-O2 for pgsql-hackers@arkaria.postgresql.org; Sun, 22 Jan 2023 21:56:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pJiKJ-0001BL-0b for pgsql-hackers@arkaria.postgresql.org; Sun, 22 Jan 2023 21:56:35 +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 1pJiKI-0001B6-MD for pgsql-hackers@lists.postgresql.org; Sun, 22 Jan 2023 21:56:34 +0000 Received: from mail-io1-xd36.google.com ([2607:f8b0:4864:20::d36]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pJiKF-0002Ov-Qn for pgsql-hackers@postgresql.org; Sun, 22 Jan 2023 21:56:33 +0000 Received: by mail-io1-xd36.google.com with SMTP id h184so4858583iof.9 for ; Sun, 22 Jan 2023 13:56:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=gWv7cvzuXOtS9ay3hkKayO//IIl/655UVOFCAAMt/UQ=; b=1d+Q4gdyOHSCobUicXbGeGL/q0XfUpvLdc6pHUPu9fszL8kG2rBe07Gr/fSk5m0+zn XUZo/fOKi8V8kaxv+aOxcTBP/UwvfIv3mTCfFH+fZVUQ6rtojqZU/tkFpmyy5pT/MkRS JgvirC9iab3pImjzCrSvw/CENCoyonlRsobz6rT68iZljdtrfeR0qY0Fdd2W1IoQdWmc obKZx+6o09rS9sb7x/fhLpR179ELcmMDIuRAhkmRJBbpTT1ZuDyTksJEtVhfV89HFOel gyNlhqiI5SgwvDjua5Yd2ZMeNuuJ6h1GxRXANLyZrgnTngd8sYyHzlwCHojZt9/OAhJ1 eDDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=gWv7cvzuXOtS9ay3hkKayO//IIl/655UVOFCAAMt/UQ=; b=AdiZUOdSJMvNSjIXsDOWvrLpK5aNAIzhcp5NzuLNqnVuZYYdsosZrXIPrvnWpsgaeP Xscsfzydwjj6Ps1YAJrG0NYXB63Dy/9zw1PIm4k0LwgNWImIusbftrR8WAubFOsgkECw /n+IJyBctT8rkJaRKbrRxJr1wfs+QGw9ho4EoZnN+VejdOtT9gdK+ICCPN4dpjkrLAz6 niWn+tsj09wCmB1nvmiNaxpubzh235tft6LRqM/TD/jGF4grmc5JQRyl6bJaP/trYKw5 NJPNKuUigGiNbtBHQ2/ife0CT70zeXoZCU6Ti6hmvalJVa3vE6bMb59K+P2qmj7fIEHj CnwA== X-Gm-Message-State: AFqh2koNHOgBMT0oQT3BMAKx+tELoCRAD4xkIFpbHI8iBWkauTmpSw0h thDG1FAbo7fbyuLA8dXqLJHOZQ== X-Google-Smtp-Source: AMrXdXvANpbZ/akRXm2dBhQigGnX5Z02aCA6ekn/sG5ilfVMJSXbX3FeSIxAaSYVM+Mzk9PJj4Cy+w== X-Received: by 2002:a05:6602:2017:b0:707:652f:e3a0 with SMTP id y23-20020a056602201700b00707652fe3a0mr11761796iod.5.1674424590585; Sun, 22 Jan 2023 13:56:30 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id l10-20020a02cd8a000000b003a7c64c31b1sm3549927jap.47.2023.01.22.13.56.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 22 Jan 2023 13:56:29 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 9EC06800A27; Sun, 22 Jan 2023 15:56:28 -0600 (CST) Date: Sun, 22 Jan 2023 15:56:28 -0600 From: Justin Pryzby To: Tom Lane Cc: Isaac Morland , Alvaro Herrera , Pavel Stehule , Magnus Hagander , pgsql-hackers@postgresql.org Subject: Re: Remove source code display from \df+? Message-ID: <20230122215628.GR13860@telsasoft.com> References: <20230122191549.5b35ulimlvz42y7l@alvherre.pgsql> <1413123.1674417854@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1413123.1674417854@sss.pgh.pa.us> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Jan 22, 2023 at 03:04:14PM -0500, Tom Lane wrote: > Isaac Morland writes: > > On Sun, 22 Jan 2023 at 14:26, Alvaro Herrera > > wrote: > >> This one would fail the sanity check that all roles created by > >> regression tests need to have names that start with "regress_". > > > Thanks for the correction. Now I feel like I've skipped some of the > > readings! > > Updated patch attached. Informally, I am adopting the regress_* policy for > > all object types. > > That's excessive. The policy Alvaro mentions applies to globally-visible > object names (i.e., database, role, and tablespace names), and it's there > to try to ensure that doing "make installcheck" against a live > installation won't clobber any non-test-created objects. There's no point > in having such a policy within a test database --- its most likely effect > there would be to increase the risk that different test scripts step on > each others' toes. If you feel a need for a name prefix for non-global > objects, use something based on the name of your test script. But we *are* talking about the role to be created to allow stable output of \df+ , so it's necessary to name it "regress_*". To appease ENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS, and to avoid clobbering global objects during "installcheck". -- Justin