Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 2E60B6329DF
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 11:15:00 -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 31536-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 14:14:52 +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 A284A6329D8
	for <pgsql-performance@postgresql.org>;
	Fri,  3 Sep 2010 11:14:52 -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 o83EEohD022002;
	Fri, 3 Sep 2010 10:14:50 -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.1009030702520.12651@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>
Comments: In-reply-to Gerhard Wiesinger <lists@wiesinger.com>
	message dated "Fri, 03 Sep 2010 07:03:55 +0200"
Date: Fri, 03 Sep 2010 10:14:50 -0400
Message-ID: <22001.1283523290@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/5
X-Sequence-Number: 40208

Gerhard Wiesinger <lists@wiesinger.com> writes:
> On Thu, 2 Sep 2010, Tom Lane wrote:
>> Hm, you sure about that?  What's in the postmaster log?

> That's the strange thing: I don't have anything in stdout/stderr log and 
> in pg_log directory and even in syslog.

Not even in that pgstartup.log file you sent stderr to?

I have seen cases before where Postgres couldn't log anything because of
SELinux.  If this is a Red Hat based system, look in the kernel log for
AVC messages.  If you see any, then SELinux is probably blocking things
because of the nonstandard directory locations.  Turning it off
temporarily would be the easiest fix, though relabeling the files would
be a better one.

			regards, tom lane