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

Update documentation regarding pg_hba (simplecluster example) #275

Open
Jorl17 opened this issue May 9, 2017 · 4 comments
Open

Update documentation regarding pg_hba (simplecluster example) #275

Jorl17 opened this issue May 9, 2017 · 4 comments

Comments

@Jorl17
Copy link

Jorl17 commented May 9, 2017

Hi! Thanks for your impressive work on stolon. We found it recently and have been trying to set it up and play with it a bit.

Unfortunately, I noticed while using your simple cluster example that it seems to be outdated because of commit eba0819 . Specifically, pg_hba.conf is no longer configured to accept local connections but this isn't clear from the simplecluster documentation (on the contrary).

Perhaps the documentation should be fixed with the appropriate information regarding usernames and passwords?

Once again, thanks for your work!

@sgotti
Copy link
Member

sgotti commented May 10, 2017

@Jorl17 Thanks!

To be sure I tested it and local connection works (but they require a password and are not trusted anymore).

In the simple example the keeper command line:

./bin/stolon-keeper --cluster-name stolon-cluster --store-backend=etcd --uid postgres0 --data-dir data/postgres0 --pg-su-password=supassword --pg-repl-username=repluser --pg-repl-password=replpassword

means that a superuser with the same name of the local user running the keeper will be created with password supassword. The when using psql you should provide the password. It works both with local connection over network that over unix socket:

psql -h 127.0.0.1 -p 5432 postgres
psql -h /tmp/ -p 5432 postgres

@Jorl17
Copy link
Author

Jorl17 commented May 12, 2017

Thanks :) I might create a PR with an update on the documentation to reflect these changes, so other new-users don't get initially confused too. Will report back soon!

@sgotti
Copy link
Member

sgotti commented May 12, 2017

@Jorl17 a PR will be great! Thanks!

@viggy28
Copy link

viggy28 commented Jun 5, 2019

Ran into this problem. If no one has started working on the PR, i can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants