| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tu Trinh Nguyenha <nguyenhatutrinh(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Can't start postgresql 11 |
| Date: | 2018-10-24 11:43:45 |
| Message-ID: | 19491.1540381425@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tu Trinh Nguyenha <nguyenhatutrinh(at)gmail(dot)com> writes:
> I am dealing with the issue of starting postgresql 11 after I upgraded to
> Mac Os Mojave yesterday.
It's unlikely this is really a Postgres bug, but ...
> The error message I have received is:" The operation couldn't be completed.
> (com.postgresapp.Postgres2.ClientLauncher error 0.)
That's pretty unhelpful :-(. A reasonable bet is that the upgrade messed
up file permissions on something, but evidently the PostgresApp wrapper
isn't going to help you find out what.
Do you get anything more useful if you try to start the postmaster by
hand, ie "postmaster -D/path/to/data/directory"?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ozan Kahramanogullari | 2018-10-24 12:02:14 | Re: psql on Mac |
| Previous Message | Tom Lane | 2018-10-24 11:22:07 | Re: psql on Mac |