Hello there, This is not necessarily a jOOQ issue, but I wonder how you would best solve it when using jOOQ. If it's too off-topic, feel free to direct me somewhere else.
We have been using jOOQ happily for a while in production; every day we have a couple of big bulk insert queries (inserting >200k records at once) that were taking ~2 minutes every time. Some days ago, we configured a parameter in our Postgres server (idle_in_transaction_session_timeout <https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-IDLE-IN-TRANSACTION-SESSION-TIMEOUT>) that kills all sessions that are in a transaction, but haven't executed any query in 30s. After implementing this configuration, these inserts started to fail. On closer inspection of a past trace where the timeout is not implemented, these are the logs on our services: 1. 23:31:53: Application starts the insert query (with returning clause) 2. 23:31:56: SQL is rendered by jOOQ and logged (3s) 3. 23:33:53: Postgres says query took 8s (after 2 minutes) 4. 23:33:54: Application fetched all results, and transaction is committed in the same second So, Postgres says the query took ~8s, but the application has been waiting for 2 minutes. We think this is because the SQL we render is very large (it's a query of the form `insert into table (column1, column2) values (1, 2), (3,4)`) and Postgres spends a lot of time parsing it, even though honestly ~2 minutes seems like a lot of time. This is not a jOOQ issue per-se, but we speculated that splitting the query up into smaller batches would solve the issue. I'm curious what options we have to do such an insert, where we also need to return the IDs of the generated records. Regards, Giovanni -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/0266d773-652a-4b46-80d0-4b5d86fbbff9n%40googlegroups.com.
