Message-ID: <gh-pgjdbc-pgjdbc-3904@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 06 Jan 2026 13:17:51 +0000
Subject: [pgjdbc/pgjdbc] issue #3904: Should this be protected with a reentrant lock?
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Id: 406518
X-GitHub-Author-Login: davecramer
X-GitHub-Issue: 3904
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-State: closed
X-GitHub-Type: issue
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3904
Content-Type: text/plain; charset=utf-8

https://github.com/pgjdbc/pgjdbc/blob/83023f3c2ae98dc69df00a560dbbe386afafe3b1/pgjdbc/src/main/java/org/postgresql/largeobject/LargeObject.java#L163

If this were called concurrently, seems like close might not be set before some operations have been done such as setting os to null