Thread

1. Can not open Postgre SQL 17.1 after update

   Большой Сэм <samattreasure@gmail.com> — 2024-11-20T11:16:23Z

   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)
   

2. Re: Can not open Postgre SQL 17.1 after update

   Thomas Munro <thomas.munro@gmail.com> — 2024-11-21T00:42:19Z

   On Thu, Nov 21, 2024 at 3:21 AM Большой Сэм <samattreasure@gmail.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
   
   
   
   

3. Re: Can not open Postgre SQL 17.1 after update

   Sandeep Thakkar <sandeep.thakkar@enterprisedb.com> — 2024-11-24T15:55:12Z

   On Thu, Nov 21, 2024 at 6:13 AM Thomas Munro <thomas.munro@gmail.com> wrote:
   
   > On Thu, Nov 21, 2024 at 3:21 AM Большой Сэм <samattreasure@gmail.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
   >
   > This error should be fixed in the updates gone out on 21st November.
   
   
   -- 
   Sandeep Thakkar