Re: 8.3devel slower than 8.2 under read-only load

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>
Subject: Re: 8.3devel slower than 8.2 under read-only load
Date: 2007-11-26 10:59:26
Message-ID: 200711261159.29762.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am Samstag, 24. November 2007 schrieb Simon Riggs:
> In many cases, 100% of queries are unprepared.

I have seen many applications where prepared queries caused stale plans and
poor performance. We have in many cases achieved great performance gains by
turning off prepared queries globally, for example in the driver layer. It
had once gotten to a point where "uses prepared statements" was on par
with "never touched postgresql.conf" and "never heard of VACUUM" as the worst
performance sins. I will gladly revisit this with 8.3, but I am not very
optimistic.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Smet 2007-11-26 11:12:38 Re: 8.3devel slower than 8.2 under read-only load
Previous Message Simon Riggs 2007-11-26 10:58:28 Re: Autovacuum and OldestXmin