Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 42C3D9F99B4 for ; Sun, 7 Oct 2007 03:06:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61703-09 for ; Sun, 7 Oct 2007 03:06:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id AD3869F9962 for ; Sun, 7 Oct 2007 03:06:53 -0300 (ADT) Received: from [192.168.1.4] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l9766lbN003237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Oct 2007 23:06:55 -0700 Message-ID: <47087723.7040403@commandprompt.com> Date: Sat, 06 Oct 2007 23:05:23 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Darren Reed CC: pgsql-admin@postgresql.org Subject: Re: Is my database now too big? References: <1191730382.18880.1214536197@webmail.messagingengine.com> In-Reply-To: <1191730382.18880.1214536197@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.1/4482/Fri Oct 5 15:43:49 2007 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Sat, 06 Oct 2007 23:06:55 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/32 X-Sequence-Number: 26946 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? > > postgres itself, however, starts up fine. > > "wc -l" of the output from the last successuful dump_all is around > 8million > lines, spread across half a dozen or so tables. > > I'm afraid that if I restructure the db to have smaller tables, I'd just > be > putting off "hitting" the ceiling. > > What can I safely do to get postgres running normally? > > I'm currently using 8.1.3, will I fare any better with a more recent > version? > > My end goal is to have maybe 50 million records. Will postgresql handle > this > (with only 1.5GB of RAM) or do I need to look elsewhere for a db of this > size? > > Thoughts? > > Cheers, > Darren > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings >