How to reproduce a bug experienced during package patch update for filing an issue?

[mike-volt]

Output of brew config

HOMEBREW_VERSION: 4.4.17
ORIGIN: https://github.com/Homebrew/brew
HEAD: 55f399c10dc7e6cc07497bdfccdecc96329e3b57
Last commit: 3 days ago
Branch: stable
Core tap JSON: 21 Jan 23:20 UTC
Core cask tap JSON: 21 Jan 23:20 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
HOMEBREW_NO_ANALYTICS: set
Homebrew Ruby: 3.3.7 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.7/bin/ruby
CPU: dodeca-core 64-bit arm_lobos
Clang: 16.0.0 build 1600
Git: 2.45.2 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.2-arm64
CLT: 16.2.0.0.1.1733547573
Xcode: N/A
Rosetta 2: false

Output of brew doctor

Your system is ready to brew.

Description of issue

I experienced this issue when an installation of postgresql@14 was upgraded from 14.12 to 14.15

the contents of $(brew --prefix)/var/postgresql@14/postmaster.opts didn't properly update:

/opt/homebrew/Cellar/postgresql@14/14.12/bin/postgres "-D" "/opt/homebrew/var/postgresql@14"

however I'm not sure how to properly reproduce this from scratch since brew install postgres@14 should install 14.15 and generate the proper postmaster.opts file

[gromgit]

As I understand it, postmaster.opts is only created/updated when the postmaster process is started, so brew upgrade postgresql@14 would (correctly) not touch that file, since that would mislead users as to which PostgreSQL version was actually running.

If you restarted PostgreSQL after upgrading from 14.12 to 14.15, and postmaster.opts still referenced the 14.12 version, then either the postmaster didn't restart, or you found a bug in PostgreSQL itself. Either way, there's nothing actionable for Homebrew here.