Re: Fatal Error KeyError: 'ck_port_range' after upgrade

From: Katherine Mcmillan <kmcmi046(at)uottawa(dot)ca>
To: Mark McMillan <mark(at)nc-mcmillans(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Fatal Error KeyError: 'ck_port_range' after upgrade
Date: 2023-06-05 14:20:46
Message-ID: YT2PR01MB9827C0E47207B1C251B98CECE84DA@YT2PR01MB9827.CANPRD01.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello Mark,

Although I cannot help with this particular error, I would like to take this opportunity to compliment you on your surname!

Have a Wonderful Day,
Katie
________________________________
From: Mark McMillan <mark(at)nc-mcmillans(dot)com>
Sent: 05 June 2023 10:11
To: pgsql-admin(at)lists(dot)postgresql(dot)org <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Fatal Error KeyError: 'ck_port_range' after upgrade

Attention : courriel externe | external email
Hello, I upgraded to pgAdmin 4 v7 (from v3 I think) on Windows and I cannot start pgAdmin any more, the fatal error says:

2023-06-05 09:51:58,190: ERROR pgadmin: Database migration failed

2023-06-05 09:51:58,194: ERROR pgadmin: Traceback (most recent call last):
File "C:\Users\Mark\AppData\Local\Programs\pgAdmin 4\v7\python\lib\site-packages\alembic\operations\batch.py", line 692, in drop_constraint
const = self.named_constraints.pop(const.name<http://const.name>)
KeyError: 'ck_port_range'

I cannot find any reference to this error in the mail list archives or online. Any help would be appreciated....

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Holger Jakobs 2023-06-05 14:33:06 Re: Fatal Error KeyError: 'ck_port_range' after upgrade
Previous Message Mark McMillan 2023-06-05 14:11:15 Fatal Error KeyError: 'ck_port_range' after upgrade