| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tanya Mamedalin" <tmamedalin(at)registrypro(dot)pro> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: signal 11 |
| Date: | 2004-01-27 00:59:15 |
| Message-ID: | 7379.1075165155@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Tanya Mamedalin" <tmamedalin(at)registrypro(dot)pro> writes:
> I was running the same Python code with Postgres 7.2.3 and psycopg 1.0.9
> with no errors. As soon as I upgraded to Postgres 7.4-0.3 and pyscopg 1.1.6
> I started getting errors when trying to execute a certain query.
BTW, this might be the same bug fixed here:
http://archives.postgresql.org/pgsql-committers/2003-11/msg00251.php
If setting "enable_hashjoin" to OFF makes the crash go away, then it
probably is the same bug, and 7.4.1 has a fix. If you still see the
problem in 7.4.1, please file a more complete bug report.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | azwa | 2004-01-27 01:42:27 | Re: time series data |
| Previous Message | Bruce Momjian | 2004-01-26 22:53:34 | Re: BUG #1059: Second Call of a PGSQL-function fails |