Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bZLqd-0007i8-VG for pgsql-admin@arkaria.postgresql.org; Mon, 15 Aug 2016 17:38:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bZLqd-0001We-IF for pgsql-admin@arkaria.postgresql.org; Mon, 15 Aug 2016 17:38:51 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bZLow-00076Q-4d for pgsql-admin@postgresql.org; Mon, 15 Aug 2016 17:37:06 +0000 Received: from resqmta-po-11v.sys.comcast.net ([2001:558:fe16:19:96:114:154:170] helo=resqmta-ch2-11v.sys.comcast.net) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bZLoo-0003EX-Vs for pgsql-admin@postgresql.org; Mon, 15 Aug 2016 17:37:04 +0000 Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-11v.sys.comcast.net with SMTP id ZLokbGoThEp5XZLombLlkF; Mon, 15 Aug 2016 17:36:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1471282616; bh=PD1E2buQT4M8doW4aEfZnql+i7tHGQFm+umS6scjHCg=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=fggvOkoQO+HTkUhyzQTvdGL1ea5xdZ6SO7xqcDCir/CMuleAMf4TE50NUWWliHYY8 EdLhQH2nhVvtMzct13HZKcCfG4ajOo+6pONPVcMsrrYE6LGRuJj1Prm3LAKFsAHqbe 3C033Ua1K2IfAslJyZmQtej3svdlF+pv9UTyNdipkRQqS0D1rov/BoilboGcvEiMzR ilhnQUoMsQyqG4Tl+WtqK1tEGzgxoufAMJjHVD0Qu8VxVhkGxKvTbTs18AmVIOP/jh RxR185P+iZ5oaFHad1wdR5cxgOYiqF66VrotwJ+bIFIUYtGsM0eUT68umFnw0Mkv2f G9etZHMUHgPpA== Received: from jerry.enova.com ([12.30.159.20]) by resomta-po-13v.sys.comcast.net with SMTP id ZLodbn9S2tLf1ZLofbvaRJ; Mon, 15 Aug 2016 17:36:54 +0000 Received: by jerry.enova.com (Postfix, from userid 1001) id 284BD740219; Mon, 15 Aug 2016 12:36:47 -0500 (CDT) From: Jerry Sievers To: pgsql-admin@postgresql.org Subject: Thanks to pg_upgrade,. we'll reclaim 1.4T of total disk !! Date: Mon, 15 Aug 2016 12:36:46 -0500 Message-ID: <86a8gerl1t.fsf@jerry.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-CMAE-Envelope: MS4wfJ5dpuX8ORjppCP4J5lzFPZ5eD6YwCkIx5Gtgjz7Mv9f4bAWhCO1U7aM1Zh6/uYefFszjMuFrxtY9PCFOa4l03JL2fFO4L2FbAviTqIeicgbcVeF/vwy tbqd2DRjwtbVpmGcA8Nev3tDWn4gwsFHCuU5fny02lQ4AMvGF1kXIwXYKOJY9djQ/2HNVmFYtCeQHA== X-Pg-Spam-Score: -2.0 (--) 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 Seriously... But I had to postpone the scheduled upgrade to investigate first. Our big warehouse ~5TB system was trial upgraded several time using snapshots and not till the last trial did I happen to notice that we were about 700G short after the upgrade. Yay! Or huh? Same warehouse had apparently crashed hard and left behind those 700G of orphaned data files unbeknownst to us. Pg_Upgrade never sees them since there is no catalog entry with a relfilenode pointing to them and thus leaves all this junk behind during the upgrade. Exactly as we would like it to. Still, the discovery was rather shocking and a couple hours of investigation ensude to explain the matter. Oh, and those 700G of space was actual logged table data, not temp or UNlogged, ergo our standby system is likewise bloated by this amount. When we do the rescheduled upgrade thus we'll be saving 1.4T. OH yeah baby!! FWIW -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin