sameersbn / sameersbn/docker-gitlab
Postgresql config file changes overwritten by container somehow. Undesirable side-effects, ie logging.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I would prefer that postgresql log directly to files using its own CSV format and rotation. This is best implemented with:
logging_collector = on
log_destination = 'csvlog'
log_filename = '%F.log'
Every time the container is restarted, the log_filename parameter is overwritten. I tried adding the parameter a second time, but then both were overwritten. This is undesirable behavior.
IMHO, whatever mechanism overwrites the file should instead do it only once or only if the file is not newer than some kind of initial initialize file (ie, postgresql.auto.conf)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the container startup mechanism that rewrites PostgreSQL settings, focusing on the log_filename parameter and postgresql.auto.conf. Reproduce the behavior across a container restart and determine whether user-provided settings are overwritten more than once. Done means the requested logging configuration remains intact after restart without duplicate parameters being rewritten.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100