Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 847C2B5DBC5 for ; Mon, 12 Sep 2011 17:55:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 64831-02 for ; Mon, 12 Sep 2011 20:55:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp2.peak6.com (smtp2.peak6.com [38.98.137.9]) by mail.postgresql.org (Postfix) with ESMTP id D3BBBB5D91F for ; Mon, 12 Sep 2011 17:55:44 -0300 (ADT) X-AuditID: 0a02cb1e-b7cbdae000007cad-ae-4e6e71d1147e Message-ID: <4E6E71CF.3020709@peak6.com> Date: Mon, 12 Sep 2011 15:55:43 -0500 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Scott Marlowe CC: Marti Raudsepp , Andy Colson , Igor Chudov , Subject: Re: Postgres for a "data warehouse", 5-10 TB References: <4E6CC458.4010206@squeakycode.net> <4E6E31DF.6020407@peak6.com> <4E6E65D8.4050403@peak6.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.220.61] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHIsWRmVeSWpSXmKPExsXCxcQrpnuxMM/P4Ml2RYtZ7fIWT99eZ7I4 vm0hk8X1meeYLZZ9Os/owOqxc9Zddo997RPZPC7sm8busfjpN+YAlqgGRpvEvLz8ksSSVIWU 1OJkW6UAV0dvM4XgksS8lMSiFAWXzOLknMTM3NQiJYXMFFslIyWFgpzE5NTc1LwSW6XEgoLU vBQlOy4FDGADVJaZp5Cal5yfkpmXbqvkGeyva2FhaqlrqGQXjwAJ3SwZa/e0sBb0c1TsXXCd sYHxAFsXIyeHhICJxO3DO1ggbDGJC/fWg8V5BTQk/v08zwpiswioSnx+Mw2shk1ATWLh7puM ILaQgKzE/lXnwGr4BYQl9n1oYgaxRQUCJBZMessIMUdQ4uTMJ2C9IgLaEo/eXAeKc3EwC/Qz Smxa+xisWVjAXuLDx2UsIAkhgTYWiU9LW9lBEpwCgRJzdnSDXcQsYCtxYc51FghbXmL72znM EFfISdxpeA5UwwH0gYLE9eX+ExiFZiHZPQtJ9ywk3QsYmVcxiheXJSZnZJoVFOeWFBjqFaQm Zpvp5aWWbGIEx/ppuR2MKy4oHmIU4GBU4uGdYJXnJ8SaWFZcmXuIUYKDWUmEd403UIg3JbGy KrUoP76oNCe1+BCjNjDQJjJLcSfnA9NQXkm8sYGBkjhv0p9MPyGBdGAqyE5NLUgtgqlm4uCU amDct9XphuLh7BZzwfTYj7smhV6b+k1gn2vLyiu5hZUOF2OUL1iKLsgKYzrf/sSLMYfpQfOR qUcD5Z/pZByceO5gssHhpbwTXH9yFmo+n3mEkT3URErF/EdeZGrojeXZhx533/S7ynzw4oF0 14b1CXMjljTVJdzasmVdTsbyDXrl7PsK7opslpygxFKckWioxVxUnAgAdSvVSwEDAAA= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.404 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201109/162 X-Sequence-Number: 44938 On 09/12/2011 03:44 PM, Scott Marlowe wrote: > The PostgreSQL team works REALLY hard to prevent any kind of > corruption scenario from rearing its ugly head, so when the word > corruption pops up I start to wonder about the system (hardware > wise) someone is using, You've apparently never used early versions of EnterpriseDB. ;) Kidding aside, it's apparently been a while since I read that particular part of the manual. The error I *was* familiar with was from the 8.0 manual: "WARNING: some databases have not been vacuumed in 1613770184 transactions HINT: Better vacuum them within 533713463 transactions, or you may have a wraparound failure." Ever since the early days, I've been so paranoid about regular vacuuming, I'm probably still a little overcautious. So, my bad. Having a database down for a few hours isn't exactly desirable, but it's certainly not corruption. :) -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604 312-676-8870 sthomas@peak6.com ______________________________________________ See http://www.peak6.com/email-disclaimer/ for terms and conditions related to this email