On 2/14/22 02:25, Lukas Eder wrote:
Until I get a handle on jooq/pgbouncer interaction I'm very
tempted by your suggestion. Since my clients particularly light
on db-interaction: get (largish) input data from server; spin for
3 day; send (lots of) results to server I don't see a downside to
StatementType.STATIC_STATEMENT. Does anything jump out to you?
PostgreSQL doesn't have a sophisticated execution plan cache.
Otherwise, static statements would be prohibitive, of course. I tend
to see this as a workaround for this specific case. It's probably
still better to investigate why the problem is happening if you have
time, but if you don't, then static statements might be good enough.
--
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/CAB4ELO7iLvnsZ9nTak90D4S2nmvGAVyuRP093E1A4N0%3DHxQ2Xg%40mail.gmail.com
<https://groups.google.com/d/msgid/jooq-user/CAB4ELO7iLvnsZ9nTak90D4S2nmvGAVyuRP093E1A4N0%3DHxQ2Xg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
As usual, it was all my fault: I did have "?prepareThreshold=0" set on
the initial proof-of-connectivity test but not set in the servlets'
context.xml.
An interesting(?) anecdote: the "missing prepared statement" error
messages all incremented the counter by two, starting at one. PS-1,
PS-3, PG-5 etc. Never an even number in almost 100 repetitions.
--
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/d3702210-6dee-69f7-8fd8-79b60b979181%40gmail.com.
