pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: mlw <markw@mohawksoft.com>
To: Mike Rogers <temp6453@hotmail.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-php@postgresql.org
Cc: pgsql-bugs@postgresql.org
Subject: Re: PostgreSQL / PHP Overrun Error
Date: Wed, 26 Sep 2001 13:15:14 -0400
Message-ID: <3BB20D22.8380C502@mohawksoft.com> (raw)
References: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com>
	<1119.1001521382@sss.pgh.pa.us>
	<OE229OEUO0UiwiL4l4800002dbf@hotmail.com>
	<3BB2089D.EEA48B34@mohawksoft.com>
	<OE32LB8TrBHxvZ9aZ1i000029b7@hotmail.com>

Interesting. I am using that same configuration. We are using the same thing on
our website as well. I have never seen this problem. Weird.

My guess is that you are getting an error. The PHP code is some how mucking
this up. But I would try executing the query in psql and see what comes up.

The PHP code than handles the error may have a fixed langth buffer for speed,
and it is to short for a longer 7.1 error message. Again, I am guessing.

My bet is that the query is failing with an error, so you really have two
problems. A problem in your SQL which is causing you to see a bug in PHP.



Mike Rogers wrote:

> Sorry:
>     PHP 4.0.6 (with memory leak patch [download listed right below
> php-4.0.6.tar.gz download- It was a problem])
>     PostgreSQL 7.1.3
>     Apache 1.3.20 (with mod_ssl- but it does the same thing without mod_ssl)
> --
> Mike
>
> ----- Original Message -----
> From: "mlw" <markw@mohawksoft.com>
> To: "Mike Rogers" <temp6453@hotmail.com>
> Cc: "Tom Lane" <tgl@sss.pgh.pa.us>; <pgsql-hackers@postgresql.org>;
> <pgsql-php@postgresql.org>; <pgsql-bugs@postgresql.org>
> Sent: Wednesday, September 26, 2001 1:55 PM
> Subject: Re: [BUGS] PostgreSQL / PHP Overrun Error
>
> > Mike Rogers wrote:
> >
> > > Well it really isn't your code (true), but the only thing that is
> changed is
> > > the 7.0-7.1-  Was a data length changed on the return or something that
> > > could affect this?
> >
> > What version of PHP are you using?
> >
> >
> >




view thread (24+ messages)  latest in thread

Message-ID: <3BB20D22.8380C502@mohawksoft.com>
Permalink:  ../3BB20D22.8380C502@mohawksoft.com/
Also on:    postgresql.org/message-id/3BB20D22.8380C502@mohawksoft.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: markw@mohawksoft.com, temp6453@hotmail.com, pgsql-hackers@postgresql.org, pgsql-bugs@postgresql.org
  Subject: Re: PostgreSQL / PHP Overrun Error
  In-Reply-To: <3BB20D22.8380C502@mohawksoft.com>
  References: <OE62aWNsvt8KBBxlIkt00002833@hotmail.com> <1119.1001521382@sss.pgh.pa.us> <OE229OEUO0UiwiL4l4800002dbf@hotmail.com> <3BB2089D.EEA48B34@mohawksoft.com> <OE32LB8TrBHxvZ9aZ1i000029b7@hotmail.com> <3BB20D22.8380C502@mohawksoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox