From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Heads-up: macOS Big Sur upgrade breaks EDB PostgreSQL installations |
Date: | 2020-11-17 10:58:42 |
Message-ID: | CA+OCxoxLsehGsxAy+k0Md8CoR_UPH3UAM9DGrnJDXXXWJjpTXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
FYI, both Jonathan and I have now tested this on additional machines and
have been unable to reproduce the issue, so it seems like something odd
happened on my original upgrade rather than a general issue.
Apologies for the noise.
On Mon, Nov 16, 2020 at 9:27 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi,
>
> This is more of a head-ups than anything else, as I suspect this may come
> up in various forums.
>
> The PostgreSQL installers for macOS (from EDB, possibly others too) create
> the data directory in /Library/PostgreSQL/<major_ver>/data. This has been
> the case since the first release, 10+ years ago.
>
> It looks like the Big Sur upgrade has taken it upon itself to "fix" any
> filesystem permissions it doesn't like. On my system, this resulted in the
> data directory having 0755 permissions, which meant that PostgreSQL refused
> to start. Manually changing the permissions back to 0700 (0750 should also
> work) fixes the issue.
>
> I'm not sure there's much we can do about this - systems that are likely
> to be affected are already out there, and we obviously don't want to relax
> the permissions Postgres requires.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EDB: http://www.enterprisedb.com
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2020-11-17 11:15:40 | Re: [HACKERS] logical decoding of two-phase transactions |
Previous Message | Heikki Linnakangas | 2020-11-17 10:38:44 | Re: Split copy. |