Message-ID: <51757655.3030101@vmware.com>
Date: Mon, 22 Apr 2013 20:41:41 +0300
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Organization: VMware
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Anne Rosset <arosset@collab.net>
CC: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Performance with the new security release
References: 
 <9A6B86D66BD3C2438AFACFA09354890F20A2A781@EXCH01.sp.corp.collab.net>
In-Reply-To: 
 <9A6B86D66BD3C2438AFACFA09354890F20A2A781@EXCH01.sp.corp.collab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 22.04.2013 19:48, Anne Rosset wrote:
> Hi,
> We are seeing some overall performance degradation in our application since we installed the security release. Other commits were also done at the same time in the application so we don't know yet if the degradation has any relationship with the security release.
> While we are digging into this, I would like to know if it is possible that the release has some impact on performance. After reading this "It was created as a side effect of a refactoring effort to make establishing new connections to a PostgreSQL server faster, and the associated code more maintainable.", I am thinking it is quite possible.

I doubt that particular commit, the one that fixed the security issue, 
could cause any meaningful slowdown. But it's not impossible that some 
other fix included in the release would cause a regression, although we 
try to be careful to avoid that. If you narrow the culprit down to the 
new PostgreSQL version, we're going to need more details to find the 
root cause.

- Heikki


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance