Re: Can not open Postgre SQL 17.1 after update

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Большой Сэм <samattreasure(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Can not open Postgre SQL 17.1 after update
Date: 2024-11-21 00:42:19
Message-ID: CA+hUKGKXYaiei33h1Ah1gOBNZCh=cxawkd5_rMrHAypV8qLJFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Nov 21, 2024 at 3:21 AM Большой Сэм <samattreasure(at)gmail(dot)com> wrote:
> I have a Macbook Air. After updating on my Mac. SQL gives this error and doesn't open after this. Tried to delete and download again but the problem is still there.
>
> _LSOpenURLsWithCompletionHandler() failed with error -54. (1)

Other reports say that this is coming from pgadmin4, not PostgreSQL,
and it started happening with the upgrade to Sequoia 15.1. No one
seems to really know why. That's an undocumented API accessed
indirectly via other libraries, so who knows, but maybe it's -54 =
permError? But apparently some people fixed it by installing a
different (newer?) build of pgadmin4. If I had to take a wild guess,
I might wonder if it has something to do with the code signing stuff
that they have been changing, but IDK.

https://github.com/pgadmin-org/pgadmin4/issues/8079

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2024-11-21 01:11:00 Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5
Previous Message Thomas Munro 2024-11-20 22:41:29 Re: [EXTERNAL] Re: BUG #18707: Installation issue