| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 8.2.4 signal 11 with large transaction |
| Date: | 2007-07-20 16:51:47 |
| Message-ID: | 10872.1184950307@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Bill Moran <wmoran(at)collaborativefusion(dot)com> writes:
> I'm now full of mystery and wonder. It would appear as if the
> underlying problem has something to do with PHP, but why should this
> cause a backend process to crash?
I'd bet on PHP submitting the query via extended query protocol
(PQexecParams or equivalent) instead of plain ol PQexec which is what
psql uses. I don't speak PHP or have it installed here, so this example
is hard for me to investigate. Can someone make a reproducer that uses
PQexecParams?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan de Visser | 2007-07-20 17:00:09 | Re: 8.2.4 signal 11 with large transaction |
| Previous Message | Bill Moran | 2007-07-20 16:16:48 | 8.2.4 signal 11 with large transaction |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan de Visser | 2007-07-20 17:00:09 | Re: 8.2.4 signal 11 with large transaction |
| Previous Message | Bill Moran | 2007-07-20 16:16:48 | 8.2.4 signal 11 with large transaction |