Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
От
Florian Weimer
Тема
Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
Дата
Msg-id
82d51q9sgf.fsf@mid.bfk.de
Ответ на
Список
Дерево обсуждения
Fragmentation of WAL files Jim Nasby <decibel@decibel.org>
Re: Fragmentation of WAL files Bill Moran <wmoran@collaborativefusion.com>
Re: Fragmentation of WAL files Tom Lane <tgl@sss.pgh.pa.us>
Re: Fragmentation of WAL files Heikki Linnakangas <heikki@enterprisedb.com>
Filesystem fragmentation (Re: Fragmentation of WAL files) Bill Moran <wmoran@collaborativefusion.com>
Re: Filesystem fragmentation (Re: Fragmentation of WAL
files) "Craig A. James" <cjames@modgraph-usa.com>
Re: Filesystem fragmentation (Re: Fragmentation of WAL files) Gregory Stark <stark@enterprisedb.com>
Re: Filesystem fragmentation (Re: Fragmentation of WAL files) Tom Lane <tgl@sss.pgh.pa.us>
Re: Filesystem fragmentation (Re: Fragmentation of WAL files) Florian Weimer <fweimer@bfk.de>
Re: Fragmentation of WAL files Greg Smith <gsmith@gregsmith.com>
* Bill Moran: > To clarify my viewpoint: > To my knowledge, there is no Unix filesystem that _suffers_ from > fragmentation. Specifically, all filessytems have some degree of > fragmentation that occurs, but every Unix filesystem that I am aware of > has built-in mechanisms to mitigate this and prevent it from becoming > a performance issue. One database engine tends to create a huge number of fragments because the files are written with holes in them. There is a significant impact on sequential reads, but that doesn't matter much because the engine doesn't implement fast, out-of-order B-tree scans anyway. 8-/ I still think that preallocating in reasonably sized chunks is beneficial. -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
В списке pgsql-performance по дате отправления