| From: | Florian Weimer <fweimer(at)bfk(dot)de> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Postgres <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is mdextend really safe? |
| Date: | 2008-08-20 10:49:34 |
| Message-ID: | 827iac55c1.fsf@mid.bfk.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Gregory Stark:
> On Unix that creates a sparse file where the intervening blocks are
> not allocated. When we later write out those blocks the filesystem
> then has to allocate space for them.
This seems to happen relatively rarely. Creating temporary holes like
this usually results in heavily fragmented files on the file systems I
use, and I don't see this with PostgreSQL. (It's one of my gripes
with Berkeley DB.)
However, I looked at the code recently and couldn't figure out *why*
PostgreSQL's observed behavior is this way. 8-(
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-08-20 11:20:51 | Re: Is mdextend really safe? |
| Previous Message | Pavel Stehule | 2008-08-20 10:38:11 | Re: proposal sql: labeled function params |