Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B5D7F9F9B64 for ; Sun, 7 Oct 2007 05:00:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 95151-04 for ; Sun, 7 Oct 2007 05:00:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by postgresql.org (Postfix) with ESMTP id 551759F9A79 for ; Sun, 7 Oct 2007 05:00:09 -0300 (ADT) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 10A7D2F85B; Sun, 7 Oct 2007 04:00:08 -0400 (EDT) Received: from web7.messagingengine.com ([10.202.2.216]) by compute1.internal (MEProxy); Sun, 07 Oct 2007 04:00:08 -0400 Received: by web7.messagingengine.com (Postfix, from userid 99) id E5FCA6F59; Sun, 7 Oct 2007 04:00:07 -0400 (EDT) Message-Id: <1191744007.14918.1214548241@webmail.messagingengine.com> X-Sasl-Enc: EeWdeHib6cTSGh8sqfQYhhEfXknAD9aL8tis1TIZgAqH 1191744007 From: "Darren Reed" To: "Joshua D. Drake" Cc: pgsql-admin@postgresql.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface References: <1191730382.18880.1214536197@webmail.messagingengine.com> <47087723.7040403@commandprompt.com> Subject: Re: Is my database now too big? In-Reply-To: <47087723.7040403@commandprompt.com> Date: Sun, 07 Oct 2007 10:00:07 +0200 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/33 X-Sequence-Number: 26947 On Sat, 06 Oct 2007 23:05:23 -0700, "Joshua D. Drake" said: > Darren Reed wrote: > > I'm starting to wonder if my database has finally grown too big for my > > computer. > > > > But, rather than peform badly, I see a number of "bad things" happen: > > > > * pg_dump fails to run, causing an "out of memory" error (I don't > > understand > > why this happens, but it does); > > > > * restarting postgres across a reboot results in tables disappearing > > without any error messages being given out (this is *really > > disturbing*.) > > Are you vacuuming? No. I'm just using the standard config If you're implying I should? The problems I've come across have become evident with as little work as this: - run "initdb" - start postgres - run "psql" to import the dumped data - run for a short period of time (less than an hour) - shutdown postgres - reboot - postgres starts - the large tables are now missing With the above, I wouldn't have thought there is enough time to do vacuums, which seem to take quite a while on large tables. The activity is a mixture of inserts and updates (from triggers and plsql functions.) Darren