From e3cabb0ba913f5a932d76654ba381a9480502d59 Mon Sep 17 00:00:00 2001 From: Prashant Pandey Date: Tue, 5 May 2026 13:57:57 +0530 Subject: [PATCH] Remove transaction isolation level config --- .../documentstore/postgres/PostgresConnectionPool.java | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/document-store/src/main/java/org/hypertrace/core/documentstore/postgres/PostgresConnectionPool.java b/document-store/src/main/java/org/hypertrace/core/documentstore/postgres/PostgresConnectionPool.java index a67b4112..74e0b20f 100644 --- a/document-store/src/main/java/org/hypertrace/core/documentstore/postgres/PostgresConnectionPool.java +++ b/document-store/src/main/java/org/hypertrace/core/documentstore/postgres/PostgresConnectionPool.java @@ -1,7 +1,5 @@ package org.hypertrace.core.documentstore.postgres; -import static java.sql.Connection.TRANSACTION_READ_COMMITTED; - import java.sql.Connection; import java.sql.SQLException; import java.time.Duration; @@ -101,7 +99,10 @@ private void setFactoryProperties( poolableConnectionFactory.setValidationQueryTimeout((int) VALIDATION_QUERY_TIMEOUT.toSeconds()); poolableConnectionFactory.setDefaultReadOnly(false); poolableConnectionFactory.setDefaultAutoCommit(true); - poolableConnectionFactory.setDefaultTransactionIsolation(TRANSACTION_READ_COMMITTED); + // Note: We intentionally do NOT call setDefaultTransactionIsolation() here. + // PostgreSQL defaults to READ_COMMITTED, which is what we want. Setting it explicitly + // causes DBCP2 to execute "SHOW TRANSACTION ISOLATION LEVEL" on every connection borrow + // (via PgConnection.getTransactionIsolation()), adding unnecessary overhead. poolableConnectionFactory.setPoolStatements(false); }