Here is a radical idea...
What is it that is causing Postgres trouble? It is the file system's attempts
to maintain some integrity. So I proposed a simple "dbfs" sort of thing which
was the most basic sort of file system possible.
I'm not sure, but I think we can test this hypothesis on the FAT32 file system
on Linux. As far as I know, FAT32 (FAT in general) is a very simple file system
and does very little during operation, except read and write the files and
manage what's been allocated. Plus, the allocation table is very simple in
comparison all the other file systems.
Would pgbench run on a system using ext2, Reiser, then FAT32 be sufficient to
get a feeling for the type of performance Postgres would get, or am I just off
the wall?
If this idea has some merit, what would be the best way to test it? Move the
pg_xlog directory first, then try base? What's the best methodology to try?
carl garland wrote:
>
> >
> > > Just put a note in the installation docs that the place where the
> >database
> > > is initialised to should be on a non-Reiser, non-XFS mount...
> >
> >Sure, we can do that now.
>
> I still think this is not necessarily the right approach either. One
> major purpose of using a journaling fs is for fast boot up time after
> crash. If you have a 100 GB database you may wish to have the data
> on XFS. I do think that the WAL log should be on a separate disk and
> on a non-journaling fs for performance.
>
> Best Regards,
> Carl Garland
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
--
I'm not offering myself as an example; every life evolves by its own laws.
------------------------
http://www.mohawksoft.com
