Re:Costs of a PostgreSQL connection
by saurik on Wednesday February 19, 2014 @06:54PM
(#7267576)
If Rails stops using the two-step parse/execute PostgreSQL commands (which are supported without issue by PGbouncer, and which is how you are supposed to get bound parameters) when prepared_statements is turned off (a setting which intuitively should only turn off using standard SQL named prepared statements), then that's pathetic behavior (even for Rails) and should really be fixed.
[ Parent
| on HN ]
There are no comments on this comment yet.