Re: Server error - Mailing list pgsql-general

From scott.marlowe
Subject Re: Server error
Date
Msg-id Pine.LNX.4.33.0305061553200.6965-100000@css120.ihs.com
Whole thread Raw
In response to Server error  (Erik Ronström <kvarken@yahoo.com>)
Responses Re: Server error  ("scott.marlowe" <scott.marlowe@ihs.com>)
Re: Server error  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

www.memtest86.com


pgsql-general by date:

Previous
From: Ralph Graulich
Date:
Subject: Re: Timebased user access
Next
From: Scott Chapman
Date:
Subject: How to hook up Access to Postgres?