We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried to do this in createcluster.conf:
initdb_options = '--locale C --encoding UTF8 --data-checksums --auth-host=scram-sha-256 --auth-local=peer'
But the generated pg_hba.conf still use md5 (my other settings come through nicely). Looking closely at the output I realized why:
Creating new PostgreSQL cluster 16/test5 ... /usr/local/opt/postgresql@16/bin/initdb --locale C --encoding UTF8 --data-checksums --auth-host=scram-sha-256 --auth-local=peer -D /usr/local/var/lib/postgresql/16/test5 --auth-local peer --auth-host md5
Would it be possible to pass the initdb_options to initdb after the default ones so they take precedence?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I tried to do this in createcluster.conf:
initdb_options = '--locale C --encoding UTF8 --data-checksums --auth-host=scram-sha-256 --auth-local=peer'
But the generated pg_hba.conf still use md5 (my other settings come through nicely). Looking closely at the output I realized why:
Creating new PostgreSQL cluster 16/test5 ... /usr/local/opt/postgresql@16/bin/initdb --locale C --encoding UTF8 --data-checksums --auth-host=scram-sha-256 --auth-local=peer -D /usr/local/var/lib/postgresql/16/test5 --auth-local peer --auth-host md5
Would it be possible to pass the initdb_options to initdb after the default ones so they take precedence?
The text was updated successfully, but these errors were encountered: