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@xxxxxxxxxxx p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
