Markus Ritter

Yes. The reason is the to get the best performance (no unnecessary parsing/converting). And I see that other libraries offer this customization as well.

[vertx.log](https://github.com/eclipse-vertx/vertx-sql-client/files/8109602/vertx.log) [jdbi.log](https://github.com/eclipse-vertx/vertx-sql-client/files/8109603/jdbi.log) Hi vietj, I attached 2 logs, one from vertx client and one from jdbi, both using TCPdump since I cannot install Wireshark in my env. By default quarkus...

I don´t know the protocol in detail but it seems that JDBI wraps all calls in BEGIN ... COMMIT (transactions) which could explain why this works since every transaction is...

I just re-validated and if I wrap every prepared statement with a transaction the code works... So the question is: does JDBI really use transactions or does it use different...

The library I use for comparison: https://jdbi.org/ Its a thin wrapper around JDBC that seems to support prepared statements in pgBouncer transaction mode. I used it since with this library...

Ok, sounds good. If you need any help please let me know

Hi, my friend fixed the docker-compose file. You may now try again...

Did you succeed with the docker file?

Sorry for the late reply. The project moved temporarily to Jdbi for now. Thanks to @shivamsriva31093 for the fixed reproducer

Hi, we have the same problem I think: we have a topic with a lot of pre-produced data and use partition ordering with batch size of 1000. Still we just...