fix(temporal): drop MySQL-only tx_isolation connectAttribute — Postgres pq driver rejected it, killing all DB connections (schema job + server) with 'no usable database connection found'
This commit is contained in:
@@ -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:
|
||||
|
||||
Reference in New Issue
Block a user