From: | Christoph Berg <cb(at)df7cb(dot)de> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | mfatticcioni(at)mbigroup(dot)it, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Best filesystem for a high load db |
Date: | 2014-11-25 16:27:18 |
Message-ID: | 20141125162718.GD21475@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Re: Bill Moran 2014-11-25 <20141125111630(dot)d05d58a9eb083c7cf80ed9f8(at)potentialtech(dot)com>
> Anything with a journal is a performance problem. PostgreSQL effectivly
> does its own journalling with the WAL logs. That's not to say that there's
> no value to crash recovery to having a journalling filesystem, but it's
> just to say that our experience showed journaling filesystems to be slower.
> That rules out ext4, unless you disable the journal. I seem to remember
> ext4 with journalling disabled being one of the faster filesystems, but I
> could be remembering wrong.
If you are using a non-journalling FS, you'll be waiting for a full
fsck after a system crash. Not sure that's an improvement.
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2014-11-25 16:54:20 | Re: Best filesystem for a high load db |
Previous Message | Bill Moran | 2014-11-25 16:16:30 | Re: Best filesystem for a high load db |