Skip to content
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

API to customise postgres.conf #246

Open
samwillis opened this issue Aug 22, 2024 · 2 comments · May be fixed by #415
Open

API to customise postgres.conf #246

samwillis opened this issue Aug 22, 2024 · 2 comments · May be fixed by #415
Labels
enhancement New feature or request

Comments

@samwillis
Copy link
Collaborator

We need a way to let users set a custom postgres.conf.

Some extensions also need to have specific things set in postgres.conf and it would be good if that could be done automatically when enabling them.

@pmp-p
Copy link
Collaborator

pmp-p commented Aug 24, 2024

That file only appears - after - initdb has run, so maybe just concat the extra conf file to it right before restart. Question is that config a user one ( that could be changed in pglite options) or specific defaults to extension and then could be in the tarball ( and applied before the dynamic link because at that stage no PGDATA/*conf has been read yet).

@pmp-p
Copy link
Collaborator

pmp-p commented Oct 12, 2024

i guess we should support both but some element of configuration are tricky because they could concern multiple extensions for the same appended line. eg https://www.postgresql.org/docs/current/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-PRELOAD related to #189

@pmp-p pmp-p added the enhancement New feature or request label Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants