Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 07019632B94
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 15:44:38 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 55108-08
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 18:44:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id A1FFC632ACE
	for <pgsql-performance@postgresql.org>;
	Fri,  3 Sep 2010 15:44:29 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o83IiSZf027254;
	Fri, 3 Sep 2010 14:44:28 -0400 (EDT)
To: Gerhard Wiesinger <lists@wiesinger.com>
cc: Pavel Stehule <pavel.stehule@gmail.com>,
	Andreas Kretschmer <akretschmer@spamfence.net>,
	pgsql-performance@postgresql.org
Subject: Re: Major performance problem after upgrade from 8.3 to 8.4 
In-reply-to: <alpine.LFD.2.01.1009032014270.11936@bbs.intern> 
References: <alpine.LFD.2.01.1008300802300.4121@bbs.intern>
	<20100830072230.GA28373@tux>
	<AANLkTi=Te9ToTG-bqVy+fHQ0wM1YWv0nhBqqYiTk2ePg@mail.gmail.com>
	<alpine.LFD.2.01.1008300956320.19598@bbs.intern>
	<AANLkTik14X_MYoZA5CHNGC8M7Rc0zXrRhoGw6FrfUPXm@mail.gmail.com>
	<alpine.LFD.2.01.1008301808330.31277@bbs.intern>
	<11111.1283185373@sss.pgh.pa.us>
	<alpine.LFD.2.01.1008301838480.4133@bbs.intern>
	<12837.1283186981@sss.pgh.pa.us>
	<alpine.LFD.2.01.1009020749380.19625@bbs.intern>
	<21281.1283433278@sss.pgh.pa.us>
	<alpine.LFD.2.01.1009030702520.12651@bbs.intern>
	<22001.1283523290@sss.pgh.pa.us>
	<alpine.LFD.2.01.1009031837550.28047@bbs.intern>
	<24994.1283532424@sss.pgh.pa.us>
	<alpine.LFD.2.01.1009031853400.31084@bbs.intern>
	<25560.1283534215@sss.pgh.pa.us>
	<alpine.LFD.2.01.1009031952390.8416@bbs.intern>
	<26620.1283537362@sss.pgh.pa.us>
	<alpine.LFD.2.01.1009032014270.11936@bbs.intern>
Comments: In-reply-to Gerhard Wiesinger <lists@wiesinger.com>
	message dated "Fri, 03 Sep 2010 20:27:04 +0200"
Date: Fri, 03 Sep 2010 14:44:28 -0400
Message-ID: <27253.1283539468@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201009/19
X-Sequence-Number: 40222

Gerhard Wiesinger <lists@wiesinger.com> writes:
> On Fri, 3 Sep 2010, Tom Lane wrote:
>> I think what may be happening here is that a postgres executable expects
>> to find itself in a full installation tree, ie if it's in /someplace/bin
>> then the timezone files are in /someplace/share, etc.  Did you do a full
>> "make install" after building, or did you just copy the postgres
>> executable?

> I just copied it as discussed in the original mail to avoid that make 
> install kills the 8.4 production RPM version:
> cp ./src/backend/postgres /bin/postgres-8.3.11

Definitely not going to work.  Instead, configure with --prefix set
to /someplace/harmless, make, make install, execute from
/someplace/harmless/bin/.

			regards, tom lane