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 1kNS7r-0003gT-8o for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Sep 2020 02:45:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kNS7p-0004pr-Oy for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Sep 2020 02:45:49 +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 1kNS7p-0004pk-J5 for pgsql-bugs@lists.postgresql.org; Wed, 30 Sep 2020 02:45:49 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kNS7j-0000m8-Bj for pgsql-bugs@lists.postgresql.org; Wed, 30 Sep 2020 02:45:49 +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 08U2jdmO805342; Tue, 29 Sep 2020 22:45:40 -0400 From: Tom Lane To: nakagawa@goodf.co.jp cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16645: pg_upgrade does not mark template1 as a system database In-reply-to: <16645-54478f8719888f75@postgresql.org> References: <16645-54478f8719888f75@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 30 Sep 2020 01:50:00 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <805340.1601433939.1@sss.pgh.pa.us> Date: Tue, 29 Sep 2020 22:45:39 -0400 Message-ID: <805341.1601433939@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > 4. Open pgAdmin 4, connect to the PostgreSQL 13.0 server and expand the > Databases node. > Expected result: > The node has [postgres]. > Actual result: > The node has [postgres] and [template1]. There's no particular concept of a "system database" in Postgres, so I don't know what pgadmin is doing to decide which databases to show or not show, but evidently it's not too well thought out. (The closest concept I can think of is whether a DB is marked datistemplate, but a test confirms that pg_upgrade successfully preserves that property on template0 and template1.) I'd suggest you file this complaint on the pgadmin lists. regards, tom lane