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" <[EMAIL PROTECTED]> > To: "Mike Rogers" <[EMAIL PROTECTED]> > Cc: "Tom Lane" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > 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? > > > > > > ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
