pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: rbygrave (@rbygrave) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
Date: Tue, 07 Jun 2022 21:35:11 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
> quite big but not crazy big - 20k rows, 10 columns
To me 20k sounds very big. Have you benchmarked that against smaller batch sizes (like batch size 1000, 100, 50, 20)?
When I benchmark test insert batching looking to find a reasonably optimal batch size I don't recall going over 1k (and generally it is way smaller batch size). I kind of think of it as approximately filling a network packet, often 100 is a good batch size but it will depend on width of columns etc.
Edit: Read the full history and the test case - very interesting re NOTIFY and size of returning content and blowing out the buffers.
view thread (36+ 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] issue #194: PgJDBC can experience client/server deadlocks during batch execution
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