Signal 11 is a segfault.
As can be seen in 'man kill'
So it is either broken hardware or broken software, in the latter case
broken postgres?
Perhaps it is usefull if you'd be able to post that plpgsql function
along?
arjen
> -----Oorspronkelijk bericht-----
> Van: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org] Namens Erik Ronström
> Verzonden: dinsdag 6 mei 2003 23:53
> Aan: pgsql-general@postgresql.org
> Onderwerp: [GENERAL] Server error
>
>
> 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.
>
> Erik
>
> __________________________________________________
> Yahoo! Plus
> For a better Internet experience
> http://www.yahoo.co.uk/btoffer
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an
> appropriate subscribe-nomail command to
> majordomo@postgresql.org so that your message can get through
> to the mailing list cleanly
>