atsalolikhin-spokeo commented on a change in pull request #10413:
URL: https://github.com/apache/airflow/pull/10413#discussion_r485787872
##########
File path: docs/howto/initialize-database.rst
##########
@@ -48,11 +48,46 @@ SqlAlchemy backend. We recommend using **MySQL** or
**Postgres**.
want to set a default schema for your role with a
command similar to ``ALTER ROLE username SET search_path = airflow,
foobar;``
+Setup your database to host Airflow
+-----------------------------------
+
+Create a database called ``airflow`` and a database user that Airflow
+will use to access this database.
+
+Example, for **MySQL**:
+
+.. code-block:: sql
+ CREATE DATABASE airflow CHARACTER SET utf8 COLLATE utf8_unicode_ci;
+ CREATE USER 'airflow' IDENTIFIED BY 'airflow';
+ GRANT ALL PRIVILEGES ON airflow.* TO 'airflow';
+
+Example, for **Postgres**:
+
+.. code-block:: sql
+ CREATE DATABASE airflow;
+ CREATE USER airflow WITH PASSWORD 'airflow';
+ GRANT ALL PRIVILEGES ON DATABASE airflow TO airflow;
+
+You may need to update your Postgres ``pg_hba.conf`` to add the
+``airflow`` user to the database access control list; and to reload
+the database configuration to load your change. See
+[The pg_hba.conf
File](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html)
+in the Postgres documentation to learn more.
+
+Configure Airflow's database connection string
+----------------------------------------------
+
Once you've setup your database to host Airflow, you'll need to alter the
-SqlAlchemy connection string located in your configuration file
-``$AIRFLOW_HOME/airflow.cfg``. You should then also change the "executor"
-setting to use "LocalExecutor", an executor that can parallelize task
-instances locally.
+SqlAlchemy connection string located in ``sql_alchemy_conn`` option in
``[core]`` section in your configuration file
+``$AIRFLOW_HOME/airflow.cfg``.
Review comment:
Okay, thank you very much! :)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
