From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] improve the pg_upgrade error message |
Date: | 2021-07-12 12:06:31 |
Message-ID: | 7c1dda7cce524e8a61edf39e9a9d538dd3fbc8e1.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2021-07-12 at 16:58 +0530, Jeevan Ladhe wrote:
> While looking into one of the pg_upgrade issue, I found it
> challenging to find out the database that has the datallowconn set to
> 'false' that was throwing following error:
>
> "All non-template0 databases must allow connections, i.e. their pg_database.datallowconn must be true"
>
> It can be argued that we can query the pg_database
> catalog and find that out easily, but at times it is challenging to get
> that from the customer environment.
>
> With attached patch, now I get following error:
> "All non-template0 databases must allow connections, i.e. their pg_database.datallowconn must be true; database "mydb" has datallowconn set to false."
I am in favor of that in principle, but I think that additional information
should be separate line.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-07-12 12:06:32 | Re: ATTACH PARTITION locking documentation for DEFAULT partitions |
Previous Message | David Rowley | 2021-07-12 12:04:22 | Re: Add proper planner support for ORDER BY / DISTINCT aggregates |