tidunguyen edited a comment on pull request #17600:
URL: https://github.com/apache/airflow/pull/17600#issuecomment-903251444


   Regarding the `utility` search_path, I thought that `utility` was required 
because my postgres setup issue was solved with that in the search_path.
   
   After digging a bit more, here is the output of a preconfigured posgresql 
from airflow official helm chart:
   
   ```
   psql (11.12)
   Type "help" for help.
   
   postgres=# \dn
     List of schemas
     Name  |  Owner
   --------+----------
    public | postgres
   (1 row)
   
   postgres=# \dt
                        List of relations
    Schema |             Name              | Type  |  Owner
   --------+-------------------------------+-------+----------
    public | ab_permission                 | table | postgres
    public | ab_permission_view            | table | postgres
    public | ab_permission_view_role       | table | postgres
    public | ab_register_user              | table | postgres
    public | ab_role                       | table | postgres
    public | ab_user                       | table | postgres
    public | ab_user_role                  | table | postgres
    public | ab_view_menu                  | table | postgres
    public | alembic_version               | table | postgres
    public | celery_taskmeta               | table | postgres
    public | celery_tasksetmeta            | table | postgres
    public | connection                    | table | postgres
    public | dag                           | table | postgres
    public | dag_code                      | table | postgres
    public | dag_pickle                    | table | postgres
    public | dag_run                       | table | postgres
    public | dag_tag                       | table | postgres
    public | import_error                  | table | postgres
    public | job                           | table | postgres
    public | log                           | table | postgres
    public | rendered_task_instance_fields | table | postgres
    public | sensor_instance               | table | postgres
    public | serialized_dag                | table | postgres
    public | sla_miss                      | table | postgres
    public | slot_pool                     | table | postgres
    public | task_fail                     | table | postgres
    public | task_instance                 | table | postgres
    public | task_reschedule               | table | postgres
    public | variable                      | table | postgres
    public | xcom                          | table | postgres
   (30 rows)
   
   postgres=# show search_path;
      search_path
   -----------------
    "$user", public
   (1 row)
   ```
   
   Only `public` schema is used here, and the search_path is `"$user", public`, 
which is the default search_path of every new postgres user. 
   
   I have also rechecked with a fresh install of airflow using pip, the default 
search_path works just fine (`psql (PostgreSQL) 12.8 (Ubuntu 
12.8-0ubuntu0.20.04.1)`)
   
   As said above, I agree with you the `utility` search_path is unnecessary. 
Moreover, I think this whole step of configuring the search_path is unnecessary 
as the installation works fine with the default search_path. Nevertheless, I do 
not guarantee that it works with older versions of Postgres.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to