Skip to content

Upgrading from postgresql@15/15.8_2 to postgresql@15/15.12_1 leads to error #211383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 of 4 tasks
paulstretenowich opened this issue Mar 18, 2025 · 3 comments
Open
3 of 4 tasks
Labels
stale No recent activity

Comments

@paulstretenowich
Copy link

paulstretenowich commented Mar 18, 2025

brew gist-logs <formula> link OR brew config AND brew doctor output

$ brew config
HOMEBREW_VERSION: 4.4.24
ORIGIN: https://github.com/Homebrew/brew
HEAD: 2f6db3757e6c8533750264c0d397c3671665e2f4
Last commit: 9 days ago
Branch: stable
Core tap JSON: 18 Mar 21:18 UTC
Core cask tap JSON: 18 Mar 21:18 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.Ce5c3QtMhx/org.xquartz:0
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 3.3.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.7/bin/ruby
CPU: octa-core 64-bit arm_ibiza
Clang: 16.0.0 build 1600
Git: 2.49.0 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.3.2-arm64
CLT: 16.2.0.0.1.1733547573
Xcode: 16.2
Rosetta 2: false

$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  icu4c@75

Verification

  • My brew doctor output says Your system is ready to brew. and am still able to reproduce my issue.
  • I ran brew update and am still able to reproduce my issue.
  • I have resolved all warnings from brew doctor and that did not fix my problem.
  • I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.

What were you trying to do (and why)?

Trying to run brew services start postgresql@15 and have the service running. What I can do though /opt/homebrew/Cellar/postgresql@15/15.12_1/bin/postgres "-D" "/opt/homebrew/var/postgresql@15" however I would prefer use the services.

What happened (include all command output)?

The service errors:

Name          Status       User          File
postgresql@15 error  19968 pstretenowich ~/Library/LaunchAgents/[email protected]

And in /opt/homebrew/var/log/[email protected]:

"root" execution of the PostgreSQL server is not permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromise.  See the documentation for
more information on how to properly start the server.

What did you expect to happen?

I expect the service to work fine as it was before the upgrade.

Step-by-step reproduction instructions (by running brew commands)

$ brew install postgresql@15
$ brew services start postgresql@15
@paulstretenowich paulstretenowich changed the title Upgrading from postgresql@15/15.12_1 to postgresql@15/15.8_2 leads to error Upgrading from postgresql@15/15.8_2 to postgresql@15/15.12_1 leads to error Mar 19, 2025
@cho-m
Copy link
Member

cho-m commented Mar 19, 2025

I tried running your steps but wasn't able to reproduce on similar machine (macOS Sequoia, ARM64).

brew install postgresql@15
...
==> Summary
🍺  /opt/homebrew/Cellar/postgresql@15/15.12_1: 3,712 files, 63MB
==> Running `brew cleanup postgresql@15`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).brew services start postgresql@15
==> Successfully started `postgresql@15` (label: homebrew.mxcl.postgresql@15)brew services list | grep postgresql@15
postgresql@15 started         cho-m ~/Library/LaunchAgents/[email protected]

Maybe something else on your machine or how you ran command?

@paulstretenowich
Copy link
Author

Thanks for testing.
What do you suggest me to test or share?
To complement, it happened after the latest OS upgrade so perhaps somehow related (Sequoia 15.3.2 (24D81))?

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale No recent activity label Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale No recent activity
Projects
None yet
Development

No branches or pull requests

2 participants