Message-ID: <gh-pgjdbc-pgjdbc-2741-c2494752607@github.com>
From: "hyragano (@hyragano)" <noreply+hyragano@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 22 Nov 2024 20:35:32 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #2741: feat: add transaction isolation mode
In-Reply-To: <gh-pgjdbc-pgjdbc-2741@github.com>
References: <gh-pgjdbc-pgjdbc-2741@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: hyragano
X-GitHub-Comment-Id: 2494752607
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2741
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/2741#issuecomment-2494752607
Content-Type: text/plain; charset=utf-8

> Hey Folks, Thanks for raising the fix for this issue. I also observe a similar data inconsistency issue with PgBouncer and transaction pooling mode. It would be better if this fix could be prioritised and more people can use it.

Actually we use it in production about 2 years from this branch however we cannot find some time to fix requested changes.