From d13489b8163a6035482a49d44678abc7a935ca52 Mon Sep 17 00:00:00 2001
From: Jelte Fennema-Nio <github-tech@jeltef.nl>
Date: Fri, 10 Jan 2025 14:44:08 +0100
Subject: [PATCH] Improve comment

---
 src/pgduckdb_hooks.cpp | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/pgduckdb_hooks.cpp b/src/pgduckdb_hooks.cpp
index 3d165467..02bd3150 100644
--- a/src/pgduckdb_hooks.cpp
+++ b/src/pgduckdb_hooks.cpp
@@ -147,8 +147,9 @@ NeedsDuckdbExecution(Query *query) {
  *
  * If there's no FROM clause, we're only selecting constants. From a
  * performance perspective there's not really a point in using DuckDB. If we
- * remove this check many common queries that are used to inspect postgres will
- * throw a warning or return incorrect results. For example:
+ * forward all of such queries to DuckDB anyway, then many queries that are
+ * used to inspect postgres will throw a warning or return incorrect results.
+ * For example:
  *
  *    SELECT current_setting('work_mem');
  *