We use the latest tag in our Docker compose which should be Postgres 16.
We use Bitnami in our Helm Chart wich should update frequently, currently it also provide Postgres 16.

So the issue is not at our side but the customer that uses an old version of Postgres, there is nothing we can do except hiding this log if really needed (but I think it's helpful). hide the warning to avoid user confusion
Consider moving to Postgres 16 or suppressing the warning from JooQ
### Feature description

![image](https://github.com/kestra-io/kestra/assets/86264395/0a1c76d8-b78f-4122-b912-8b4fd9be904a)

core/src/main/resources/logback/text.xml
core/src/main/resources/logback/text.xml
diff --git a/core/src/main/resources/logback/text.xml b/core/src/main/resources/logback/text.xml
index 94efdaee06..32ee92c27b 100644
--- a/core/src/main/resources/logback/text.xml
+++ b/core/src/main/resources/logback/text.xml
@@ -24,7 +24,14 @@
         </filter>
         <filter class="ch.qos.logback.core.filter.EvaluatorFilter">
             <evaluator>
-                <expression>return message.contains("outOfOrder mode is active. Migration of schema");</expression>
+                <!--
+                    - Disabling Liquibase outOfOrder warning
+                    - Disabling JooQ POSTGRES version support warning, see https://github.com/kestra-io/kestra/issues/3321#issuecomment-2017665833
+                -->
+                <expression>
+                    return message.contains("outOfOrder mode is active. Migration of schema") ||
+                        message.contains("Database version is older than what dialect POSTGRES supports");
+                </expression>
             </evaluator>
             <OnMismatch>NEUTRAL</OnMismatch>
             <OnMatch>DENY</OnMatch>
