Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 40D499FBBB3 for ; Mon, 14 May 2007 12:13:33 -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 05727-04-2 for ; Mon, 14 May 2007 12:13:30 -0300 (ADT) X-Greylist: delayed 02:00:02.958483 by SQLgrey-1.7.4 Received: from mail1.sun.ac.za (mail1.sun.ac.za [146.232.64.12]) by postgresql.org (Postfix) with ESMTP id 8F44D9FBBBB for ; Mon, 14 May 2007 12:13:29 -0300 (ADT) Received: from burger.sun.ac.za ([146.232.128.30]) by mail1.sun.ac.za with esmtp (Exim 4.50) id 1HncEn-0008Tp-Vz for pgsql-admin@postgresql.org; Mon, 14 May 2007 17:13:26 +0200 Received: from js by burger.sun.ac.za with local (Exim 4.63) (envelope-from ) id 1HncEn-0007yD-Ui for pgsql-admin@postgresql.org; Mon, 14 May 2007 17:13:25 +0200 Date: Mon, 14 May 2007 17:13:25 +0200 From: Johann Spies To: pgsql-admin@postgresql.org Subject: Re: ERROR: invalid memory alloc request size Message-ID: <20070514151325.GB30367@sun.ac.za> Mail-Followup-To: Johann Spies , pgsql-admin@postgresql.org References: <20070514131318.GA26537@sun.ac.za> <11217.1179153258@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11217.1179153258@sss.pgh.pa.us> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.772 tagged_above=0 required=5 tests=AWL=0.957, BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 200705/113 X-Sequence-Number: 25433 On Mon, May 14, 2007 at 10:34:18AM -0400, Tom Lane wrote: > Johann Spies writes: > > I am using postgresql 8.1 on Debian Stable. > > 8.1.what? Sorry. The version is 8.1.8-1 > > > psql:laai_squid_logs:4: ERROR: invalid memory alloc request size 1350958157 > > CONTEXT: COPY squidlogs, line 238780099 > > Is this repeatable? Yes. > Is it always the same line and same bogus request size? > Yes - the same line. I am not 100% certain that it is the same bogus request size. I will test it overnight again. It takes a long time. > If Postgres was built with debug symbols it would be useful to get a > stack trace to try to figure out more about what's happening. If you > want to try that, attach to the backend with gdb while the COPY is > running, then do > > $ gdb /path/to/postgres PID-of-backend > gdb> b errfinish > gdb> cont > ... wait for breakpoint to be hit ... > gdb> bt > gdb> q > answer 'y' to ok-to-detach prompt > Unfortunately gdb reports "no debugging symbols found". I will try and recompile postgresql with debugging symbols and try again. Thanks. Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch "Yea, though I walk through the valley of the shadow of death, I will fear no evil, for thou art with me; thy rod and thy staff they comfort me." Psalms 23:4