From f560767eb0e074d76499eaae43cc27c7461dc6e8 Mon Sep 17 00:00:00 2001 From: Mihir Kandoi Date: Tue, 30 Jun 2026 20:58:52 +0530 Subject: [PATCH] =?UTF-8?q?ci(postgres):=20include=20=C2=A76=20in=20the=20?= =?UTF-8?q?How-to-review=20closing=20summary?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The closing paragraph named only the §2/§3 semantic divergences as static-checker-invisible; §6 (refactor/conversion row-set changes) is equally invisible and belongs there too. (greptile nit.) Co-Authored-By: Claude Opus 4.8 --- .github/POSTGRES_COMPATIBILITY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/POSTGRES_COMPATIBILITY.md b/.github/POSTGRES_COMPATIBILITY.md index 19d0cee1862..6f2445d8d44 100644 --- a/.github/POSTGRES_COMPATIBILITY.md +++ b/.github/POSTGRES_COMPATIBILITY.md @@ -206,5 +206,5 @@ Prefer a comment that names the rule (e.g. "loose GROUP BY — Max()-wrap, don't splits the row count") so the fix is unambiguous. The static pre-commit checker (`.github/helper/postgres_compat.py`) catches the *mechanical* -§1 breaks; the **semantic** §2/§3 divergences are exactly what a reviewer (and this guide) must -cover, because no static check can see them. +§1 breaks; the **semantic** §2/§3 divergences and the §6 refactor/conversion row-set changes are +exactly what a reviewer (and this guide) must cover, because no static check can see them.