X-Original-To: pgsql-general-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id AB7089FA7BA
	for <pgsql-general-postgresql.org@postgresql.org>;
	Wed, 16 Aug 2006 11:31:48 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 92885-06 for
	<pgsql-general-postgresql.org@postgresql.org>;
	Wed, 16 Aug 2006 14:31:39 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 3E2359FA65C
	for <pgsql-general@postgresql.org>;
	Wed, 16 Aug 2006 11:31:39 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7GEVZjl019839;
	Wed, 16 Aug 2006 10:31:35 -0400 (EDT)
To: =?ISO-8859-1?Q?Poul_M=F8ller_Hansen?= <freebsd@pbnet.dk>
cc: pgsql-general@postgresql.org
Subject: Re: Segmentation Fault 
In-reply-to: <44E308B2.8030008@pbnet.dk> 
References: <44E308B2.8030008@pbnet.dk>
Comments: In-reply-to =?ISO-8859-1?Q?Poul_M=F8ller_Hansen?= <freebsd@pbnet.dk>
	message dated "Wed, 16 Aug 2006 13:59:46 +0200"
Date: Wed, 16 Aug 2006 10:31:34 -0400
Message-ID: <19838.1155738694@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200608/720
X-Sequence-Number: 99491

=?ISO-8859-1?Q?Poul_M=F8ller_Hansen?= <freebsd@pbnet.dk> writes:
> Last night one of my databases broke down temporary because of a 
> segmentation fault.

> At 00:36:21 this was happening in the pgsql log
> 2006-08-16 00:36:21 CEST - LOG:  duration: 14673.110 ms  statement: 
> EXECUTE <unn
> amed>  [PREPARE:  select * from app.insert_unitstat($1,$2,$3,$4,$5,$6,$7,
> $8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21)  as result]
> ...
> These statements are called in a plpgsql function and the function is 
> called via JDBC

Given that you're using duration logging and JDBC, I wonder whether you
didn't trip over this recently-identified bug:
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00815.php
Patch is here:
http://archives.postgresql.org/pgsql-committers/2006-08/msg00278.php

			regards, tom lane