ensure PostgreSQL log_destination is set to 'stderr' #185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some packages - I'm looking at FreeBSD here:
https://github.com/freebsd/freebsd-ports/blob/main/databases/postgresql14-server/files/patch-src_backend_utils_misc_postgresql.conf.sample
set log_destination to a non-standard value in the postgresql.conf
template. CP_Testing.pm relies on the log output to detect server
start and is defeated by this packaging.
Instead of arguing with package maintainers, just force-set
log_destination to 'stderr' and have CP_Testing.pm do it's work.