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 1kNVJq-0002UF-Mn for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Sep 2020 06:10:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kNVJp-0001zz-KG for pgsql-bugs@arkaria.postgresql.org; Wed, 30 Sep 2020 06:10:25 +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 1kNTSl-0006YX-QY for pgsql-bugs@lists.postgresql.org; Wed, 30 Sep 2020 04:11:31 +0000 Received: from mail-pf1-x441.google.com ([2607:f8b0:4864:20::441]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kNTSe-0006Ha-AH for pgsql-bugs@lists.postgresql.org; Wed, 30 Sep 2020 04:11:29 +0000 Received: by mail-pf1-x441.google.com with SMTP id x123so264747pfc.7 for ; Tue, 29 Sep 2020 21:11:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=goodf-co-jp.20150623.gappssmtp.com; s=20150623; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=pEjLEcCFejgG0lc/+gNhAnpZ3TWQykj7ygwyT3db4rk=; b=mI4FirPYCtu8XHj2v4kZ/umNuFDQ4rEn8nWIdfaAedsNBnu04bOKv0nJ22DH8VqSNW gq5VZMYuPbUiz8PvZ4YCH1bn6E+mZGsTitZDraFdywrHt8S/JnafTcH5KfASD+U03IYd BxBJMTi7gpwgbtvo6QuAHO9H6zZeoWvvg26t3/KyRr82vNZpT6Apsq2LUUDiavtFOgvd m6Na0OGDaltaVuxpxXmuv1bc0UuQyMXrbK4SZg3rgCZ/Y0qsvUaRCSVWmOa2fELDjs1Q +k29r768+WivYTrddqeoJ8MDbHIKr2p/A6gZXN9/9jBgXV2DNrx5nLTLjQAMLd/GAD48 n3ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=pEjLEcCFejgG0lc/+gNhAnpZ3TWQykj7ygwyT3db4rk=; b=g/L/gDKCm2a2Pz30fl7JTm0SoyBJTUZ+0EdNNRmntFkjWQMLF2qELRAPcpx+Y2aIdf MfrEfh9R9XQoKbpW+uz2Iz9ozzPC4dKXzD7+jZKs5wW7CmlJ1N48zEKEQNa3jUQuwrky foFxrfpFrTZxAbkI2X7ARggonsOtzi1ULCerwGtrQtYIPrFxPOwil65B2PvE5zVZVevX lZ8Z33Sg6tn1QohuPNoOban219ZWhL3fgCRaoJKsjybu+C+gGP0O/bycNB0/Nm2QoADa 6e4Y38Nvjf9XswjZMm5WntPIOm3URpr6uV4OlXarxUWCvoiHnLtWTTH+7VAzeyiSOgzf 6Bzw== X-Gm-Message-State: AOAM530rntPf3EMA8AwVuB8bNGLFhpA4KzZrJvMvkAJFEQ8pl+Ahm4Ew iyzulSEbvtN3YVtKs1A0RzQozC+DOfm3NNRYi/Y= X-Google-Smtp-Source: ABdhPJyX+hLTFHMunkjK5KQh3V2LC5JL/kskM9iOZa/BzTtYW9UTFMnmrEz72Ocsvu+o0gyfRRNiXA== X-Received: by 2002:a63:5401:: with SMTP id i1mr632920pgb.398.1601439082020; Tue, 29 Sep 2020 21:11:22 -0700 (PDT) Received: from nakagawapc ([2400:4050:ce82:3200:3c50:5b33:ef1:4658]) by smtp.gmail.com with ESMTPSA id j12sm431712pjs.21.2020.09.29.21.11.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Sep 2020 21:11:21 -0700 (PDT) From: "Y. NAKAGAWA" To: "'Tom Lane'" Cc: References: <16645-54478f8719888f75@postgresql.org> <805341.1601433939@sss.pgh.pa.us> In-Reply-To: <805341.1601433939@sss.pgh.pa.us> Subject: RE: BUG #16645: pg_upgrade does not mark template1 as a system database Date: Wed, 30 Sep 2020 13:11:19 +0900 Message-ID: <029201d696df$c1542940$43fc7bc0$@goodf.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHs0qAEtk9udE4MsrHrs0gcmS+JZwF574pkqUg0w8A= Content-Language: ja List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Thank you for your suggestion. According to pgAdmin4, [System database?] is [No] and [Template?] is [Yes]. I will post this to the pgadmin lists later. Regards, -- Nakagawa, Y. -----Original Message----- From: Tom Lane Sent: Wednesday, September 30, 2020 11:46 AM 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 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