Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U8H1X-00029K-Hm for pgsql-admin@arkaria.postgresql.org; Wed, 20 Feb 2013 21:16:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U8H1W-0005WV-P6 for pgsql-admin@arkaria.postgresql.org; Wed, 20 Feb 2013 21:16:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U8H1V-0005Vm-QS for pgsql-admin@postgresql.org; Wed, 20 Feb 2013 21:16:17 +0000 Received: from mail-ia0-x22d.google.com ([2607:f8b0:4001:c02::22d]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U8H1P-0000oA-Bw for pgsql-admin@postgresql.org; Wed, 20 Feb 2013 21:16:16 +0000 Received: by mail-ia0-f173.google.com with SMTP id h37so7619226iak.4 for ; Wed, 20 Feb 2013 13:16:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=y6fB+P67x1/mOvE9gYs40RVMcSAx/snxZfpKTCz1IOI=; b=nd35DdAkOPtnSl6/STPn89cbB/DDeA/DunsuwNcxV+jd40g4X8w+f3v17TO0/XPJQR QwdUytIIW9FkcG7CaoXOlVhvDqEvLSD0aVdfjFMD+wRnpodOA+EFRq7xvEhvi3UupN21 15FUpGffWNwT/1bb4xqHlZB2cxOP2ntZ8/VwJkjyPffHSsv4vvMW3Y3clFiWtTwQOV4M 8FLxMq0KvGKpqR/FNaH60smxsGUFs6c9UJquStihsKL5r5bcWvhkeTRdDvoI9Z7L2c5A b5nmitsu9t0M6O2T4Td375mLw2bCmH3d5Zdf26EZDjF2lho9iTFrCaYPT/5EV0ObMnQz c2HQ== X-Received: by 10.50.186.169 with SMTP id fl9mr4144497igc.72.1361394969517; Wed, 20 Feb 2013 13:16:09 -0800 (PST) Received: from [192.168.2.100] ([65.101.225.90]) by mx.google.com with ESMTPS id xc3sm14630191igb.10.2013.02.20.13.16.07 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 20 Feb 2013 13:16:08 -0800 (PST) Message-ID: <51253CF4.3030706@consistentstate.com> Date: Wed, 20 Feb 2013 14:15:32 -0700 From: Brian Fehrle User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120314 Thunderbird/10.0.3 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Migrating tables to new tablespace, freed up space doesn't match moved data Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkH+J4v3zqbE9aMz0sPhgjeN0dNFw6OGlNqIAptfMMszwQBv0VZ6MhyFlH1ykedmTMsH4/k X-Pg-Spam-Score: -1.9 (-) 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 Hi all, I've set up a tablespace on a different partition from the main data directory. I moved a few tables and indexes over to the new tablespace and the disk space used in this new tablespace doesn't match the amount of data 'freed up' from the main data directory. The tablespace is sitting at 15 GB used, but the space freed up on the main partition is about 10 GB. Any thoughts as to why I didn't see as much space freed up as I thought I would? Thanks, - Brian F -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin