Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 987BA9FC08E for ; Thu, 18 Oct 2007 11:56:10 -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 17988-06-3 for ; Thu, 18 Oct 2007 11:56:08 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 835F79FC0AE for ; Thu, 18 Oct 2007 11:56:07 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so439332ugf for ; Thu, 18 Oct 2007 07:56:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=WaYs/rkIQX/rRVGPFaZJtW3/DbydWGgFr48HFnLZXtI=; b=A8RjYNBNx7tS9CDq0tDCU9GsQOJq7rfbseFqEjjeIsnGeg3pG9G+4AUxz31oWVaxIECHMq1yoeM/cQHukleyxHF4qilFnBqHE7W3a5pwk/IKDmnj+iZ9n+wZUDpThLPwZmmFsG1XgRwI5j+bzQ4a+I6s9E5OIvyJn1S/d1AwdLM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=te+2uwNKL+bFFnE3yb0Kd7tqA3ezZWHMrCPD6l8vgsppDxeMwx7c4LblbUBUDyAt+GjA6JdxtVJMkHVcYR8PfF5itWXkSFokWuZVU7KmUH1lEbu2c6e5qUPJrFsSMV6aG1YmmuR6PyNN9xlF7lFE7GGVQAFHI+62SE6nPmi/phI= Received: by 10.67.119.15 with SMTP id w15mr1910056ugm.1192719365778; Thu, 18 Oct 2007 07:56:05 -0700 (PDT) Received: by 10.67.29.6 with HTTP; Thu, 18 Oct 2007 07:56:05 -0700 (PDT) Message-ID: Date: Thu, 18 Oct 2007 09:56:05 -0500 From: "Scott Marlowe" To: "Darren Reed" Subject: Re: Is my database now too big? Cc: "Tom Lane" , "Joshua D. Drake" , pgsql-admin@postgresql.org In-Reply-To: <4715FD90.8020607@fastmail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1191730382.18880.1214536197@webmail.messagingengine.com> <4712E15B.8000405@fastmail.net> <17093.1192464190@sss.pgh.pa.us> <4713CA8C.5020303@fastmail.net> <471435D1.4030806@fastmail.net> <47145B27.9030200@fastmail.net> <4715FC35.5020902@fastmail.net> <4715FD90.8020607@fastmail.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/169 X-Sequence-Number: 27083 On 10/17/07, Darren Reed wrote: > Darren Reed wrote: > > For better or worse, it seems to be behaving itself again for a while... > > > > There was, however, one change to my procedure and that was to > > drop the triggers/functions when restoring the data (using copy into). > > Perhaps I spoke too soon... > > # /usr/pkg/bin/pg_dumpall -O -U postgres -a > /data/dumpall > pg_dump: [archiver (db)] connection to database "template1" failed: > FATAL: out of memory > DETAIL: Failed on request of size 20. > pg_dumpall: pg_dump failed on database "template1", exiting > > ...for better or worse, I'm interfacing to postgresql using perl's DBI > interface. > Are there likely to be any issues from that? (Although I can't see how > a client > should be able to cause the server to become corrupt unless there's a bug in > the server.) Perl and DBI are fine. You really need to stop using an alpha release of an OS though. There's no way to know if the problems you're experiencing are coming from that or something else. Once you're on a stable OS release, start testing again and let us know if anything breaks. But like Tom likes to say, if postgresql breaks running on an alpha OS release, you get to keep both pieces.