From: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 8.2.4 signal 11 with large transaction |
Date: | 2007-07-20 17:17:04 |
Message-ID: | 20070720131704.f76af31d.wmoran@collaborativefusion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
In response to Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> 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.
Doesn't appear that way. The PHP source is somewhat cryptic, but I
don't seem much ambiguity here:
pgsql_result = PQexec(pgsql, Z_STRVAL_PP(query));
There're no conditional blocks around that, so it's the only possible
choice when pg_query() gets called in a PHP script. PHP exposes a
seperate pg_query_params() that wraps PQexecParams().
> 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?
Is there any way that this (or something similar) could still apply?
--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/
wmoran(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-07-20 17:56:01 | Re: 8.2.4 signal 11 with large transaction |
Previous Message | Jan de Visser | 2007-07-20 17:00:09 | Re: 8.2.4 signal 11 with large transaction |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2007-07-20 17:42:34 | Re: MAXIMUM_ALIGNOF on Windows-32 |
Previous Message | Jan de Visser | 2007-07-20 17:00:09 | Re: 8.2.4 signal 11 with large transaction |