pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Johann Spies <jspies@sun.ac.za>
To: pgsql-admin@postgresql.org
Subject: Re: ERROR: invalid memory alloc request size
Date: Thu, 17 May 2007 15:20:33 +0200
Message-ID: <20070517132033.GA9482@sun.ac.za> (raw)
In-Reply-To: <5221.1179337804@sss.pgh.pa.us>
References: <20070514131318.GA26537@sun.ac.za>
	<11217.1179153258@sss.pgh.pa.us>
	<20070515105042.GA8121@burger.sun.ac.za>
	<5221.1179337804@sss.pgh.pa.us>

On Wed, May 16, 2007 at 01:50:04PM -0400, Tom Lane wrote:

> You got the wrong process then --- maybe the postmaster itself rather
> than the backend assigned to your psql session?  You can identify the
> backend PID via pg_backend_pid() within the psql session of interest,
> or look in pg_stat_activity.

Thanks.  I have now activated gdb on three sub-process busy with the
query as far as I can determine.  The first one was the the writer
process which reached a breakpoint before the query ended.  Here is the
output:

Program received signal SIGINT, Interrupt.
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7c5b03d in select () from /lib/tls/i686/cmov/libc.so.6
#2  0x082a8dff in pg_usleep ()
#3  0x081c1862 in BackgroundWriterMain ()
#4  0x080cbf71 in BootstrapMain ()
#5  0x081c6c87 in ClosePostmasterPorts ()
#6  0x081cab77 in PostmasterMain ()
#7  <signal handler called>
#8  0xffffe410 in __kernel_vsyscall ()
#9  0xb7c5b03d in select () from /lib/tls/i686/cmov/libc.so.6
#10 0x081c8037 in ClosePostmasterPorts ()
#11 0x081c9924 in PostmasterMain ()
#12 0x081823b5 in main ()
(gdb) q


Another one that happened before an error message from psql.  I typed
'cont' after this output and the error message from psql followed
thereafter.


Breakpoint 1, 0x0827eef6 in errfinish ()
(gdb) bt
#0  0x0827eef6 in errfinish ()
#1  0x0828039c in elog_finish ()
#2  0x082993b3 in MemoryContextAlloc ()
#3  0x0828d437 in pg_mb2wchar ()
#4  0x0811c288 in CreateCopyDestReceiver ()
#5  0x0811ea43 in DoCopy ()
#6  0x081f9d00 in ProcessUtility ()
#7  0x081f6ed9 in PostgresMain ()
#8  0x081f7cac in FreeQueryDesc ()
#9  0x081f84d9 in PortalRun ()
#10 0x081f3b51 in pg_parse_query ()
#11 0x081f5296 in PostgresMain ()
#12 0x081c8a1f in ClosePostmasterPorts ()
#13 0x081c9924 in PostmasterMain ()
#14 0x081823b5 in main ()


Regards
Johann
-- 
Johann Spies          Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch

     "Jesus said unto her, I am the resurrection, and the 
      life. He that believeth in me, though he were dead, 
      yet shall he live."          John 11:25         



view thread (19+ messages)  latest in thread

Message-ID: <20070517132033.GA9482@sun.ac.za>
Permalink:  ../20070517132033.GA9482@sun.ac.za/
Also on:    postgresql.org/message-id/20070517132033.GA9482@sun.ac.za

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jspies@sun.ac.za
  Subject: Re: ERROR: invalid memory alloc request size
  In-Reply-To: <20070517132033.GA9482@sun.ac.za>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox