| From: | Scott Carey <scott(at)richrelevance(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com>, Craig James <craig_james(at)emolecules(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: limiting performance impact of wal archiving. |
| Date: | 2009-11-12 06:37:02 |
| Message-ID: | C720ED0E.167A3%scott@richrelevance.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> Using ext2 means that you're still exposed to fsck errors on boot after
> a crash, which doesn't lose anything but you have to go out of your way
> to verify you're not going to get stuck with your server down in that
> case. The state of things on the performance side is nicely benchmarked
> at
> http://www.commandprompt.com/blogs/joshua_drake/2008/04/is_that_performance_i_
> smell_ext2_vs_ext3_on_50_spindles_testing_for_postgresql/
>
fsck on a filesystem with 1 folder and <checkpoint_segments> files is very
very fast. Even if using WAL archiving, there won't be many
files/directories to check. Fsck is not an issue if the partition is
exclusively for WAL. You can even mount it direct, and avoid having the OS
cache those pages if you are using a caching raid controller.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2009-11-12 06:47:35 | Re: limiting performance impact of wal archiving. |
| Previous Message | Ing . Marcos Luís Ortíz Valmaseda | 2009-11-12 06:04:53 | Re: Why age (datfrozenxid) in postgres becomes 1073742202 not zero after each vacuum of database. |