From: Alexander Fortin <alexander.fortin@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: pg_database_size() and actual disk space usage
Date: Fri, 20 Apr 2012 13:04:32 +0200
Message-ID: <4F9142C0.80008@gmail.com> (raw)
In-Reply-To: <4F758796.6090000@innogames.de>
References: <4F742D3A.8010501@gmail.com>
<CA+h6AhgGgREbgpt2bobXUzunppWRbgii2TYMSksSbeYouM9Agg@mail.gmail.com>
<4F743C47.1040907@gmail.com>
<4F746282.3060406@innogames.de>
<4F755EBE.2070908@gmail.com>
<4F758796.6090000@innogames.de>
On 3/30/12 12:14 PM, Bernhard Schrader wrote:
>
> Ok, well with Kernel 2.6.38 xfs introduced a new "feature" (i think it
> was dynamic preallocation) which caused some strange behaviour for me
> also, i discussed it on xfs mailinglist, maybe this gives you some hints
> of solving your different diskusages.
>
> http://old.nabble.com/Problems-with-filesizes-on-different-Kernels-td33342207.html#a33342207
>
>
> At the end was the solution for me, but you can first check what i
> posted in the first message - testing base directory with du -sh and du
> --apparent-size -h
>
> i hope this will help you.
Hi Bernhard,
just to say thank you to have pointed this out, it actually seems to be
related to this "dynamic speculative EOF preallocation" feature of XFS.
For the records, I've done a couple of checks and I can see clearly that
it's definitely unrelated to Postgres (apparently seems that I can
reproduce the change of data occupation on the XFS file system just
accessing those files).
Talk soon,
--
Alexander Fortin
http://about.me/alexanderfortin/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alexander.fortin@gmail.com
Subject: Re: pg_database_size() and actual disk space usage
In-Reply-To: <4F9142C0.80008@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox