From: Tom Lane <tgl@sss.pgh.pa.us>
To: Poul Møller Hansen <freebsd@pbnet.dk>
Cc: pgsql-general@postgresql.org
Subject: Re: Segmentation Fault
Date: Wed, 16 Aug 2006 16:21:19 -0400
Message-ID: <28314.1155759679@sss.pgh.pa.us> (raw)
In-Reply-To: <44E337BB.2030708@pbnet.dk>
References: <44E308B2.8030008@pbnet.dk>
<19838.1155738694@sss.pgh.pa.us>
<44E337BB.2030708@pbnet.dk>
=?ISO-8859-1?Q?Poul_M=F8ller_Hansen?= <freebsd@pbnet.dk> writes:
>> 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> Sorry but didn't, but I noticed this:
> Also I must notice that the segfault only occur if
> log_min_duration_statement is set to 0
I don't believe that statement actually ... it might have chanced to act
that way in one or two trials for Sergey, but since the bug essentially
consists in access to already-freed-and-perhaps-reused memory, it's not
very predictable whether it will fail visibly or not. In any case the
problem could occur for any duration-logging attempt.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, freebsd@pbnet.dk
Subject: Re: Segmentation Fault
In-Reply-To: <28314.1155759679@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox