You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please excuse me if this been discussed already (I have searched). I have recently explored the possibility of using a connection pooler for Postgresql named PgBouncer. This works most efficiently if each sql call can be independent but that is not the case if using stored procedures. The only alternative if I am not mistaken is using non parameterized simple strings which of course is very clunky and possibly unsafe.
Have it been discussed to use e.g. PQexecParams (https://www.postgresql.org/docs/current/libpq-exec.html) or other ways of executing queries with parameters but not using prepared statements?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Please excuse me if this been discussed already (I have searched). I have recently explored the possibility of using a connection pooler for Postgresql named PgBouncer. This works most efficiently if each sql call can be independent but that is not the case if using stored procedures. The only alternative if I am not mistaken is using non parameterized simple strings which of course is very clunky and possibly unsafe.
Have it been discussed to use e.g. PQexecParams (https://www.postgresql.org/docs/current/libpq-exec.html) or other ways of executing queries with parameters but not using prepared statements?
With best regards from Sweden
/Johan R
Beta Was this translation helpful? Give feedback.
All reactions