On 03/24/2016 11:21 PM, Merlin Moncure wrote:
>> Personally I think the right solution would be to add support for prepared
>> statements in pgbouncer, and have pgbouncer run PREPARE as necessary, either
>> after opening a new connection to the database or at the first use of a
>> given prepared statement in a connection.
>
> maybe so. A while back I was running a hacked pgbouncer that had
> support for async notifications (i still have the code around
> somewhere). It can be done -- however this not a complete solution;
> both LISTEN and PREPARE are possible from within server-side
> functions.
Yes, it is not a complete solution, but it solves the problems of many
users. I think even just supporting the protocol level prepare and
execute commands would be enough for many of those who have problems
with pgbouncer.
Andreas
