Skip site navigation (1) Skip section navigation (2)

Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3)

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>,"Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Date: 2006-11-28 12:04:18
Message-ID: E1539E0ED7043848906A8FF995BDA579018FE16D@m0143.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
 
> I don't doubt that there may be a positive effect from increasing the 
> block size.  But we haven't seen any analysis of why that 
> might be.  If it's just to use the disk system bandwith better, maybe
we should 
> combine page writes instead or something.

It is usually the reads that need aid. Writes are fast on modern
disksystems since they are
cached.

I think the main effect is reduced OS overhead for the readahead
prediction logic and
reduced system call overhead.

Andreas

In response to

pgsql-hackers by date

Next:From: Michael MeskesDate: 2006-11-28 12:44:28
Subject: Re: ecpg_config.h not installed
Previous:From: Zeugswetter Andreas ADI SDDate: 2006-11-28 11:58:55
Subject: Re: Potential to_char localization bug

pgsql-patches by date

Next:From: Andrew SullivanDate: 2006-11-28 16:40:39
Subject: Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3)
Previous:From: Simon RiggsDate: 2006-11-28 09:22:37
Subject: Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group