multi-node ubuntu changes #1055
Conversation
|
|
||
| **4. Start database servers, create Citus extension** | ||
|
|
||
| :: | ||
|
|
||
| # start the db server | ||
| sudo service postgresql restart | ||
| or |
There was a problem hiding this comment.
Can you explain more about why we present alternatives here? When would someone choose to restart postgresql vs postgresql@14-main ?
There was a problem hiding this comment.
The idea is to ensure that someone does not start the server on another Postgres server. I had this issue where it started on a 9.5 server instead of 14. Someone would use postgres@14-main to ensure connection to postgres14, another person can use restart Postgres if they are sure their server is already on 14. Which would be the note about ps - ef.
We could eliminate the option entirely and allow users to only use one.
| # and make it start automatically when computer does | ||
| sudo update-rc.d postgresql enable | ||
|
|
||
| .. note:: | ||
| Ensure you are starting the right postges version. You can check this by running ``ps -ef | grep Postgres`` |
There was a problem hiding this comment.
Could the ps -ef ... be woven into the restart commands above? Ideally we could have the script itself detect the right service to restart.
There was a problem hiding this comment.
Yes, that would be the best thing to do to ensure users are starting the right thing automatically.
There was a problem hiding this comment.
Hi @francisjodi, are you interested in submitting a change to automate the script's restart logic, by means of ps -ef ... or otherwise?
No description provided.