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.

Sign up for GitHub

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

multi-node ubuntu changes #1055

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

multi-node ubuntu changes #1055

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions installation/multi_node_debian.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,15 +59,21 @@ Before starting the database let's change its access permissions. By default the

.. note::
Your DNS settings may differ. Also these settings are too permissive for some environments, see our notes about :ref:`worker_security`. The PostgreSQL manual `explains how <http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html>`_ to make them more restrictive.
Based on your DNS you can add another line with your IP address to allow the host unrestricted access, if you do not have an IP address that begins with 10.*.*.*. Otherwise add the line given for IPV4 address space.

**4. Start database servers, create Citus extension**

::

# start the db server
sudo service postgresql restart
or
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain more about why we present alternatives here? When would someone choose to restart postgresql vs postgresql@14-main ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

sudo systemctl restart postgresql@14-main
# 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``
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could the ps -ef ... be woven into the restart commands above? Ideally we could have the script itself detect the right service to restart.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that would be the best thing to do to ensure users are starting the right thing automatically.


You must add the Citus extension to **every database** you would like to use in a cluster. The following example adds the extension to the default database which is named `postgres`.

Expand Down