From 01a310d13fee7ac7a7217400799c32a999cb42e1 Mon Sep 17 00:00:00 2001
From: Story Crater Bot <19826264+Riotpiaole@users.noreply.github.com>
Date: Tue, 21 Jul 2026 22:02:07 -0700
Subject: [PATCH] =?UTF-8?q?fix(temporal):=20drop=20MySQL-only=20tx=5Fisola?=
 =?UTF-8?q?tion=20connectAttribute=20=E2=80=94=20Postgres=20pq=20driver=20?=
 =?UTF-8?q?rejected=20it,=20killing=20all=20DB=20connections=20(schema=20j?=
 =?UTF-8?q?ob=20+=20server)=20with=20'no=20usable=20database=20connection?=
 =?UTF-8?q?=20found'?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 k8s/applications/temporal/temporal-values.yaml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/k8s/applications/temporal/temporal-values.yaml b/k8s/applications/temporal/temporal-values.yaml
index 7d44ee9..c48acae 100644
--- a/k8s/applications/temporal/temporal-values.yaml
+++ b/k8s/applications/temporal/temporal-values.yaml
@@ -107,8 +107,12 @@ server:
           maxConns: 20
           maxIdleConns: 10
           maxConnLifetime: "1h"
-          connectAttributes:
-            tx_isolation: "READ-COMMITTED"
+          # NOTE: no `connectAttributes: { tx_isolation: ... }` here — tx_isolation
+          # is a MySQL-only connection parameter. The Postgres `pq` driver rejects
+          # it ("unrecognized configuration parameter"), which killed every DB
+          # connection (schema-setup job AND server) with the misleading
+          # "no usable database connection found". Postgres defaults to READ
+          # COMMITTED isolation anyway, so nothing is lost by omitting it.
       visibility:
         driver: "sql"
         sql: