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
Sent: 14 September 2023 1
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
On 9/14/23 00:15, Ryo Yamaji (Fujitsu) wrote:
Hi all
I am planning to migrate from PostgreSQL9.2 to PostgreSQL14.7.
Running the same SQL with the same statistics as previous versions resulted in
different access plans.
I have no knowledge of the PostgreSQL planner and would like to be informed
On Fri, 15 Sept 2023 at 01:36, Ryo Yamaji (Fujitsu)
wrote:
> Question:
> I am assuming that the version upgrade has changed the behavior of the
> planner. Is this correct?
It's possible. 9.2 was a long time ago. It would be quite a bit of
work to determine if this is the case. You could perhap
> On 14 Sep 2023, at 12:50, SMITH Matt wrote:
>
> Starting the newer pgAdmin results a timeout error on the UI and the
> following errors in the pgAdmin log file
Are you absolutely sure you are connecting to the right instance with the right
connection parameters (hostname, port, TLS settings,
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.
Then I used the pg_u
Hi all
I am planning to migrate from PostgreSQL9.2 to PostgreSQL14.7.
Running the same SQL with the same statistics as previous versions resulted in
different access plans.
I have no knowledge of the PostgreSQL planner and would like to be informed.
Please assist.
Behavior:
I am using an envi
