Subject: Re: upgraded to pgsql 8.2.4, getting worse performance
	then 7.4.x
From: Reid Thompson <Reid.Thompson@ateb.com>
Reply-To: Reid.Thompson@ateb.com
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Douglas J Hunley <doug@hunley.homeip.net>,
 pgsql-performance@postgresql.org
In-Reply-To: <1577.1180927042@sss.pgh.pa.us>
References: <200706020913.32241.doug@hunley.homeip.net>
	<8862.1180797911@sss.pgh.pa.us>
	<200706031329.07857.doug@hunley.homeip.net>
	<1577.1180927042@sss.pgh.pa.us>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Mon, 04 Jun 2007 10:28:45 -0400
Message-Id: <1180967325.6175.18.camel@jhereg>
Mime-Version: 1.0

On Sun, 2007-06-03 at 23:17 -0400, Tom Lane wrote:
> Douglas J Hunley <doug@hunley.homeip.net> writes:
> > On Saturday 02 June 2007 11:25:11 Tom Lane wrote:
> >> Another thing that seems strange is that the 8.2 config file does not
> >> seem to have been processed by initdb --- or did you explicitly comment
> >> out the settings it made?
> 
> > I don't understand this comment. You are saying 'initdb' will make changes to
> > the file? The file I sent is the working copy from the machine in question.
> 
> Yeah --- in a normal installation, initdb will provide un-commented
> entries for these postgresql.conf parameters:
> 
> max_connections
> shared_buffers
> max_fsm_pages
> datestyle
> lc_messages
> lc_monetary
> lc_numeric
> lc_time
> 
> (The first three are set dependent on SHMMAX probing, the others
> dependent on locale.)  Your conf file doesn't seem to have been through
> that autoconfiguration step, which suggests someone poking at things
> they should have left alone.
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org

A WAG, but perhaps the new conf file was overwritten after installation
with the one from the 'old' installation '..because that's the
configuration that we've already tweaked and was working...'