From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mike Broers <mbroers@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres block size alignment with filesystem block size
Date: Wed, 13 Jun 2012 13:52:14 -0400
Message-ID: <20120613175214.GA4418@momjian.us> (raw)
In-Reply-To: <11681.1338999875@sss.pgh.pa.us>
References: <CAB9893gSq_A4njV6XfAeZ_f7ZN4ES3_Qz=Bidq16k90RoRfPsA@mail.gmail.com>
<11681.1338999875@sss.pgh.pa.us>
On Wed, Jun 06, 2012 at 12:24:35PM -0400, Tom Lane wrote:
> Mike Broers <mbroers@gmail.com> writes:
> > Hello, I am setting up a new postgres production server in a managed
> > hosting environment. I dont have much insight into the underlying disk
> > architecture but the filesystem I have been presented with has a 4k block
> > size. Postgres defaults to 8k block size; would it be beneficial to repave
> > the filesystem at an 8k block size or problematic to leave it at 4k?
>
> I doubt it's worth the trouble to change it. Most filesystems default
> to 4k or smaller block sizes, so that's what PG is accustomed to run on.
> I think it would only really be an issue if PG's block size weren't a
> multiple of the filesystem block.
I have heard about performance issues when the virtual machine block
size isn't aligned with the host OS block size.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, mbroers@gmail.com
Subject: Re: postgres block size alignment with filesystem block size
In-Reply-To: <20120613175214.GA4418@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox