| From: | Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Большой Сэм <samattreasure(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Can not open Postgre SQL 17.1 after update |
| Date: | 2024-11-24 15:55:12 |
| Message-ID: | CANFyU97r5oY2J1niijLeL+5eBzBz1tSj=DW=Pv3hFHRGddsu-Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Nov 21, 2024 at 6:13 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> 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
>
> This error should be fixed in the updates gone out on 21st November.
--
Sandeep Thakkar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2024-11-24 19:07:26 | Re: Detection of hadware feature => please do not use signal |
| Previous Message | Tom Lane | 2024-11-24 01:42:00 | Re: BUG #18722: Processing arrays with plpgsql raises errors |