| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | 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-23 20:10:13 |
| Message-ID: | 20160323201013.GQ3127@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin,
* Merlin Moncure (mmoncure(at)gmail(dot)com) wrote:
> No one is arguing that that you should send it any every time (at
> least -- I hope not).
I'm not sure I follow how you can avoid that though?
pgbouncer in transaction pooling mode may let a particular connection
die off and then, when you issue a new request, create a new one- which
won't have any prepared queries in it, even though you never lost your
connection to pgbouncer.
That's why I was saying you'd have to send it at the start of every
transaction, which does add to network load and requires parsing, etc.
Would be nice to avoid that, if possible, but I'm not quite sure how.
One thought might be to have the server somehow have a pre-canned set of
queries already set up and ready for you to use when you connect,
without any need to explicitly prepare them, etc.
Just a thought. I do still like the general idea of INE support for
PREPARE, but perhaps there's a better option.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2016-03-23 20:18:35 | Re: VS 2015 support in src/tools/msvc |
| Previous Message | Merlin Moncure | 2016-03-23 20:08:32 | Re: NOT EXIST for PREPARE |