Message-ID: From: "davecramer (@davecramer)" To: "pgjdbc/pgjdbc" Date: Tue, 18 Mar 2025 22:38:18 +0000 Subject: Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921) In-Reply-To: References: List-Id: X-GitHub-Author-Login: davecramer X-GitHub-Comment-Id: 2734889280 X-GitHub-Comment-Type: issue_comment X-GitHub-Issue: 943 X-GitHub-Repo: pgjdbc/pgjdbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/943#issuecomment-2734889280 Content-Type: text/plain; charset=utf-8 > > [SQLServerConnection is not thread-safe, however multiple statements created from a single connection can be processing simultaneously in concurrent threads.](https://docs.microsoft.com/en-us/sql/connect/jdbc/reference/sqlserverconnection-class?view=sql-server-ver15) > > I just came across this while looking for more specific documentation on the behaviour of the postgresql driver when result sets from a single connection are processed by multiple threads. The last comment is from 2021. Are the proposed changes now obsolete? It looks like TimestampUtils is no longer a static class. What issues are you running into?