hpereira98 opened a new issue, #40116:
URL: https://github.com/apache/airflow/issues/40116

   ### Apache Airflow Provider(s)
   
   postgres
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-postgres==5.7.1
   
   ### Apache Airflow version
   
   2.9.1
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Other 3rd-party Helm chart
   
   ### Deployment details
   
   Airflow deployed in remote K8s cluster and locally using a Minikube cluster.
   
   ### What happened
   
   We've upgraded our Airflow instance from 1.10.12 to 2.9.1.
   We were previously using `PostgresOperator` to trigger the execution of a 
few PostgreSQL functions, which had `RAISE NOTICE` statements to print some 
important information regarding the functions execution.
   In the previous version we were using, we could see those logs in the Web UI,
   However, after the upgrade, we stopped seeing these.
   We've tried:
   - configuring `client_min_messages` and `log_min_messages` to `NOTICE` in 
the database level;
   - changing `PostgresOperator` to the new `SQLExecuteQueryOperator`;
   - setting the operator's parameter `show_return_value_in_logs` to true.
   None of these seem to allow these logs being shown.
   
   ### What you think should happen instead
   
   `RAISE NOTICE` statements should be shown in the DAGs logs.
   
   ### How to reproduce
   
   1. Set up Airflow instance with version 1.10.12.
   2. Create Dummy DAG that triggers a PostgreSQL function with a `RAISE 
NOTICE` statement.
   3. See logs printed in the Web UI for that DAG execution.
   4. Upgrade Airflow to 2.9.1.
   5. Trigger same DAG.
   6. Stop seeing the same logs printed in the Web UI.
   
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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