Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TOXry-00068J-80 for pgsql-admin@postgresql.org; Wed, 17 Oct 2012 17:57:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TOXrt-0002rM-Sw for pgsql-admin@postgresql.org; Wed, 17 Oct 2012 17:57:25 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q9HHvJxD028052; Wed, 17 Oct 2012 13:57:19 -0400 (EDT) From: Tom Lane To: Neil Morgan cc: "pgsql-admin@postgresql.org" Subject: Re: pg_dump out of memory In-reply-to: References: Comments: In-reply-to Neil Morgan message dated "Wed, 17 Oct 2012 17:07:34 -0000" Date: Wed, 17 Oct 2012 13:57:19 -0400 Message-ID: <28051.1350496639@sss.pgh.pa.us> X-Pg-Spam-Score: -2.3 (--) X-Archive-Number: 201210/58 X-Sequence-Number: 40174 Neil Morgan writes: > I am running a PostgreSQL 8.3 server (not my choice, would prefer 9.1) but I am experiencing memory issues when using pg_dump. 8.3.what? > Does anyone have any ideas please? For starters, turn on log_statements so you can see what query is triggering this. It'd be even better if you can get a stack trace from the point of the errfinish call. https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend regards, tom lane