Viktor Holmberg <v(at)viktorh(dot)net> writes:
> I haven’t checked the source code, but yes the isn_weak feature has some footgun potential. As it doesn’t respect transactions, but rather sets a flag on session level, it’s easy for the “isn weakness” to leak out into a connection pool.
Yeah, really that ought to be a GUC I should think. There isn't
anything well-designed about it ...
I found some prior discussion here:
https://www.postgresql.org/message-id/flat/C12AE0A2A752416C79F3EE81%40teje
but we don't seem to have pulled the trigger on changing anything.
regards, tom lane