| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | Re: NOT EXIST for PREPARE |
| Date: | 2016-03-24 22:32:42 |
| Message-ID: | 56F46B0A.6060309@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-24 22:38:18 | Re: Using quicksort for every external sort run |
| Previous Message | Merlin Moncure | 2016-03-24 22:21:14 | Re: NOT EXIST for PREPARE |