Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 1CD129FB8B2 for ; Wed, 17 Oct 2007 09:18:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 01998-04 for ; Wed, 17 Oct 2007 09:18:17 -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 B31069FBB62 for ; Wed, 17 Oct 2007 09:18:17 -0300 (ADT) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 9129E32E85; Wed, 17 Oct 2007 08:18:16 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 17 Oct 2007 08:18:16 -0400 X-Sasl-enc: yNBbGZVh31M7w/9nSNgLzrNM+1iSlTcZM2lc1gvoWw3B 1192623495 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 391541B66; Wed, 17 Oct 2007 08:18:15 -0400 (EDT) Message-ID: <4715FD90.8020607@fastmail.net> Date: Wed, 17 Oct 2007 05:18:24 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Scott Marlowe CC: Tom Lane , "Joshua D. Drake" , pgsql-admin@postgresql.org Subject: Re: Is my database now too big? References: <1191730382.18880.1214536197@webmail.messagingengine.com> <47097EA7.902@fastmail.net> <4712D97E.7010004@fastmail.net> <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> In-Reply-To: <4715FC35.5020902@fastmail.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/153 X-Sequence-Number: 27067 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.) Darren