BUG #4564: multi threaded queries corrupt client when server debugging levels are hi

From: "Diez Roggisch" <diez(dot)roggisch(at)ableton(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4564: multi threaded queries corrupt client when server debugging levels are hi
Date: 2008-12-05 11:40:47
Message-ID: 200812051140.mB5Bel79069491@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 4564
Logged by: Diez Roggisch
Email address: diez(dot)roggisch(at)ableton(dot)com
PostgreSQL version: 8.3
Operating system: Debian Lenny
Description: multi threaded queries corrupt client when server
debugging levels are hi
Details:

We yesterday hunted down a bug that made our
python/psycopg2/libpq.so.5-based apache processes segfault at random.

In the end, we could reproduce the error with this script

http://www.initd.org/svn/psycopg/psycopg2/trunk/examples/threads.py

locally on the machine, regardless of tcp or socket being used.

It occured after turning all logging facilities like log_min_error_statement
to the highest level possible.

The problem can't be reproduced on my developer machine (ubuntu hardy)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marc Schablewski 2008-12-05 14:17:59 BUG #4565: nextval not updated during wal replication, leading to pk violations
Previous Message Eugene Pimenov 2008-12-05 10:57:29 BUG #4563: Translation of errors.