Re: BUG #16645: pg_upgrade does not mark template1 as a system database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nakagawa(at)goodf(dot)co(dot)jp
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16645: pg_upgrade does not mark template1 as a system database
Date: 2020-09-30 02:45:39
Message-ID: 805341.1601433939@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2020-09-30 02:57:31 Re: BUG #16636: Upper case issue in JSONB type
Previous Message Tom Lane 2020-09-30 02:21:34 Re: BUG #16644: null value for defaults in OLD variable for trigger