=?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
