| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Shay Rojansky <roji(at)roji(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Greg Stark <stark(at)mit(dot)edu>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Slowness of extended protocol |
| Date: | 2016-08-10 17:00:41 |
| Message-ID: | 20160810170041.GJ4028@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Vladimir Sitnikov (sitnikov(dot)vladimir(at)gmail(dot)com) wrote:
> 3) "suddently get slow the 6th time" is a PostgreSQL bug that both fails to
> estimate cardinality properly, and it does not provide administrator a way
> to disable the feature (generic vs specific plan).
Dropping and recreating the prepared statement is how that particular
issue is addressed.
> Query cache does have very good results for the overall web page times, and
> problems like "6th execution" are not that often.
While it may have good results in many cases, it's not accurate to say
that using prepared statements will always be faster than not.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2016-08-10 17:10:00 | Re: Proposal for CSN based snapshots |
| Previous Message | Alexander Korotkov | 2016-08-10 16:54:07 | Re: Proposal for CSN based snapshots |