From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | <gitarrerik(at)musiker(dot)nu> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Server error |
Date: | 2003-05-06 21:54:02 |
Message-ID: | Pine.LNX.4.33.0305061553200.6965-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 6 May 2003, Erik Ronström wrote:
> Hello,
>
> I have a plpgsql function which dies strangely very often, with the
> message "server closed the connection unexpectedly". The log file says
>
> [...]
> postgres[3315]: [391-8] :extprm () :locprm () :initplan <> :nprm 0
> :scanrelid 1 }
> postgres[30748]: [182] DEBUG: reaping dead processes
> postgres[30748]: [183] DEBUG: child process (pid 3315) was terminated
> by signal 11
> postgres[30748]: [184] DEBUG: server process (pid 3315) was terminated
> by signal 11
> postgres[30748]: [185] DEBUG: terminating any other active server
> processes
> postgres[30748]: [186] DEBUG: all server processes terminated;
> reinitializing shared memory and semaphores
> postgres[30748]: [187] DEBUG: shmem_exit(0)
> [...]
>
> What is signal 11 (and where is it documented anyway?), and what could
> be the cause? I tracked the error to a line in the function which
> consists of a simple EXECUTE call.
Sig 11 means you have bad memory or CPU, about 99.9% of the time.
From | Date | Subject | |
---|---|---|---|
Next Message | Ralph Graulich | 2003-05-06 21:54:15 | Re: Timebased user access |
Previous Message | Erik Ronström | 2003-05-06 21:53:22 | Server error |