pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: SMITH Matt <Matt.SMITH@uk.thalesgroup.com>
To: Adrian Klaver <adrian.klaver@aklaver.com>
To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: RE: Help with PostgreSQL Upgrade
Date: Thu, 14 Sep 2023 15:37:55 +0000
Message-ID: <c452a479a4164625ae6aa5fb7c365a58@uk.thalesgroup.com> (raw)
In-Reply-To: <93ba9f39-196b-4f1e-3b57-43e4f9a0173d@aklaver.com>
References: <99c8bc7733fb4a558a6f58c9e06addf3@uk.thalesgroup.com>
	<93ba9f39-196b-4f1e-3b57-43e4f9a0173d@aklaver.com>

Classified as: {OPEN}

Hi,

Thanks for the messages. It looks like the problem lay in spurious "junk" on the path environment variable.
Tidying that up results in pgAdmin being perfectly happy post migration.

Matt


{OPEN}

-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: 14 September 2023 16:25
To: SMITH Matt <Matt.SMITH@uk.thalesgroup.com>; pgsql-general@postgresql.org
Subject: [EXTERNAL EMAIL] Re: Help with PostgreSQL Upgrade

On 9/14/23 03:50, SMITH Matt wrote:
> Classified as: {OPEN}
>
>
> Hi,
>
> We currently have a database hosted in pg 13.1 (with PostGIS 3.1.1)
> and we are keen to move to pg 15.3 (with PostGIS 3.3.3) all running on
> Windows 10.
>
> I installed pg15 without issue. The pgAdmin 4 utility (bundled with
> postgres 15) connects okay.
>

> Our apps and services seem happy with the new pg15 database.
>
> However, using the pg_upgrade.exe utility to migrate our db has
> resulted in some sort of issue whereby pgAdmin (the version bundled
> with 15) will no longer access our server.
>

> 2023-09-12 15:04:12,182: ERROR    pgadmin:    Exception when checking
> for update

This seems to an internal pgAdmin4 issue with what looks to be it's internal update check trying to call home. Is there a firewall that prevents that on your network?

You might have more luck with getting a complete answer on the pgAdmin-support list:

https://www.postgresql.org/list/pgadmin-support/

--
Adrian Klaver
adrian.klaver@aklaver.com
The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform the originator immediately and delete it and all copies from your system.

Thales UK Limited. A company registered in England and Wales. Registered Office: 350 Longwater Avenue, Green Park, Reading, Berks RG2 6GF. Registered Number: 868273

Please consider the environment before printing a hard copy of this e-mail.


view thread (4+ messages)

Message-ID: <c452a479a4164625ae6aa5fb7c365a58@uk.thalesgroup.com>
Permalink:  ../c452a479a4164625ae6aa5fb7c365a58@uk.thalesgroup.com/
Also on:    postgresql.org/message-id/c452a479a4164625ae6aa5fb7c365a58@uk.thalesgroup.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: Matt.SMITH@uk.thalesgroup.com, adrian.klaver@aklaver.com
  Subject: Re: Help with PostgreSQL Upgrade
  In-Reply-To: <c452a479a4164625ae6aa5fb7c365a58@uk.thalesgroup.com>
  References: <99c8bc7733fb4a558a6f58c9e06addf3@uk.thalesgroup.com> <93ba9f39-196b-4f1e-3b57-43e4f9a0173d@aklaver.com> <c452a479a4164625ae6aa5fb7c365a58@uk.thalesgroup.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox