Date: Tue, 14 Oct 2003 11:42:37 -0700
From: Sean Chittenden <sean@chittenden.org>
To: Ivan Voras <ivoras@fer.hr>
Cc: pgsql-performance@postgresql.org
Subject: Re: go for a script! / ex:  PostgreSQL vs. MySQL
Message-ID: <20031014184237.GA21028@perrin.nxad.com>
References: <20031012213527.BB2B61CB4664@svr4.postgresql.org>
	<00af01c39112$d9ac4350$bf8ec6c1@flatline>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00af01c39112$d9ac4350$bf8ec6c1@flatline>
User-Agent: Mutt/1.5.4i

> >>     This would be parameters such as the block size and a few
> >> other compile time parameters. If we can get to some of these
> >> read-only parameters than that would make this step easier,
> >> certainly for the new recruits amongst us.
> >
> > Actually, from my perspective, we shouldn't bother with this; if an admin
> > knows enough to set an alternate blaock size for PG, then they know
> > enough to tweak the Conf file by hand.  I think we should just issue a
> > warning that this script:
> > 1) does not work for anyone who is using non-default block sizes,
> 
> There was some talk, either on this list or freebsd-performance
> about setting the default block size for PostgreSQL running on
> FreeBSD to be 16k because of performance reasons. That is: *default*
> for the port, user is not asked.

Real quick, this isn't true, the block size is tunable, but does not
change the default.  You can set PGBLOCKSIZE to the values "16K" or
"32K" to change the block size, but the default remains 8K.

http://lists.freebsd.org/pipermail/freebsd-database/2003-October/000111.html

-sc

-- 
Sean Chittenden