Re: Block_Size on NTFS

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: postgresqlgeneral(dot)domain(dot)thewild_codata(at)spamgourmet(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Block_Size on NTFS
Date: 2009-06-09 12:32:16
Message-ID: 4A2E5650.1050802@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bruce Momjian wrote:
> postgresqlgeneral(dot)domain(dot)thewild_codata(at)spamgourmet(dot)com wrote:
>> Hi all !
>>
>> Reading through the list of settings returned by "SHOW ALL", I noticed
>> the "block_size" variable, which defaults to 8192.
>>
>> Running on Windows Server, my data directory is on an NTFS partition.
>> Running CHKDSK on this partition tells me that there are "4096 bytes in
>> each allocation unit."
>>
>> Are these allocation units the same as the "block_size", or does this
>> only have to do with disk geometry ?
>> If they are the same, is it important that they match ?
>
> It is not necessary they match. It just means that Postgres extends
> files in 8k chunks while your file system extends them in 4k chunks.

... though it's a really good idea that the Pg block size be a multiple
of the file system block size. Since most file systems use blocks of 4k
or some other 2^x power less than that, Pg's 8k block size is basically
always going to be fine.

New hard disks are moving to 4k physical blocks, so you won't have any
issues on new 4k block disks either.

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message postgresqlgeneral.domain.thewild_codata 2009-06-09 12:33:44 Re: Block_Size on NTFS
Previous Message Martin Gainty 2009-06-09 12:20:44 Re: Sum of multiplied deltas