pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: sehrope (@sehrope) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
Date: Mon, 11 Sep 2017 11:10:24 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> On the other hand, threading issues (e.g. reusing a connection across threads) are quite common, so adding some safety still makes sense.
Not if it's going to be for something that's internal or not required to be safe. Otherwise it's just added complexity and overhead.
Unless the entire usage of a Connection is thread safe there's no real gain in being partially thread safe anyway. If anything it's scarier as other unhandled edge cases would be encountered.
Better to be explicit that it's not intended to be used by multiple threads (outside of say `.cancel()`) and not deal with any of this.
view thread (29+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox