Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VZLmG-00085a-Pe for pgsql-admin@arkaria.postgresql.org; Thu, 24 Oct 2013 14:20:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VZLmG-000650-8X for pgsql-admin@arkaria.postgresql.org; Thu, 24 Oct 2013 14:20:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VZLmF-00063x-6r for pgsql-admin@postgresql.org; Thu, 24 Oct 2013 14:20:43 +0000 Received: from mail3.neteven.com ([37.59.178.241]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VZLm7-0003Ol-LO for pgsql-admin@postgresql.org; Thu, 24 Oct 2013 14:20:42 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail3.neteven.com (Postfix) with ESMTP id E1CFE140BC1 for ; Thu, 24 Oct 2013 16:20:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail3.neteven.com Received: from mail3.neteven.com ([127.0.0.1]) by localhost (mail3.neteven.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcGZN3XxR+W9 for ; Thu, 24 Oct 2013 16:20:33 +0200 (CEST) Received: from [192.168.1.34] (unknown [159.180.255.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail3.neteven.com (Postfix) with ESMTPSA id 985D61407A5 for ; Thu, 24 Oct 2013 16:20:33 +0200 (CEST) Message-ID: <52692CCC.8080305@neteven.com> Date: Thu, 24 Oct 2013 16:21:00 +0200 From: Thomas SIMON User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Huge increase of database partition Content-Type: multipart/alternative; boundary="------------050005090407050606040301" X-Pg-Spam-Score: -2.3 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------050005090407050606040301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi the list, Yesterday, i have had a big problem of disk space on my server, running postgresql 9.0.13; with streaming replication. Between 6pm and 7-30pm, i went from 45% used space to 99% (100% ?) used space on my /data partition (who contains my postgresql/9.0/main/base ; but does not contains the WAL; they are deported on an other partition). - seen only after with munin - Juste after that - still according to munin- , the partition suddently decreases to its normal value (around 45%) This peak represents around 165 Go of data ! ; beacause my partition size is 315 Go. I can't explain why, it's the first time i have something like this. Usually, the size of the partition is very stable ; and grows very slowly. Still with munin, i see that in this period, the blocks read per second increases from around 20k to 80k, and i see that the disk utilisation is around 100%, which confirms that postgres wrote a lot of data. I don't understand how this can happen, have you ever seen things like this ? Thanks in advance, Thomas --------------050005090407050606040301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi the list,

Yesterday, i have had a big problem of disk space on my server, running postgresql 9.0.13; with streaming replication.

Between 6pm and 7-30pm, i went from 45% used space to 99% (100% ?) used space on my /data partition (who contains my postgresql/9.0/main/base ; but does not contains the WAL; they are deported on an other partition). - seen only after with munin -

Juste after that - still according to munin- , the partition suddently decreases to its normal value (around 45%)
This peak represents around 165 Go of data ! ; beacause my partition size is 315 Go.

I can't explain why, it's the first time i have something like this. Usually, the size of the partition is very stable ; and grows very slowly.
Still with munin, i see that in this period, the blocks read per second increases from around 20k to 80k,  and i see that the disk utilisation is around 100%, which confirms that postgres wrote a lot of data.

I don't understand how this can happen, have you ever seen things like this ?

Thanks in advance,
Thomas


--------------050005090407050606040301--