Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: 8.2.4 signal 11 with large transaction


  • 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: Fri, 20 Jul 2007 13:17:04 -0400
  • Message-id: <20070720131704(dot)f76af31d(dot)wmoran(at)collaborativefusion(dot)com>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group