suggested block size for a frequently updated postgresql?

[Dryice Liu]

Oliver Fromme <olli at lurza.secnetix.de> wrote:

> Dryice Liu <dryice at hotpop.com> wrote:
>  > I'm planning on setting up a postgresql server, the database data
>  > files are on their own slice so I can tune the file system for pgsql.
>  > 
>  > The database is pretty large. On my test server, some data files get
>  > larger than 1G and is splitted by pgsql. Also the database will be
>  > updated frequently.
>  > 
>  > I'm planning on setting the slice with a bigger block size/fragment
>  > size but not sure if that's a good idea. I know the default on FreeBSD
>  > is 16K/2K, I'm planning on something like 1M/128K.
>
> So, the bottom line is:  I recommend you leave the bsize
> and fsize at the default 16K/2K.  However, you probably
> should reduce the inode density from the default, i.e. use
> the -i option with some high value such as 262144 (that's
> 2^18).  But don't make this value too high either ...
> I remember someone tried to set it to 64 million or some-
> thing, which broke his FS.

Thanks for the detail explanation and suggestion!

-- 
Dryice @ http://dryice.3322.org

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/sylvester-response.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-database/attachments/20051112/3d07481e/attachment.bin