Re: Re: Bug #1379 Updated: PHP3 does not return full pages when databases are accessed
| From: | Sascha Schumann | Date: | Thu, 06 May 1999 16:38:40 +0000 |
| Subject: | Re: Re: Bug #1379 Updated: PHP3 does not return full pages when databases are accessed | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-5396@lists.php.net to get a copy of this message | ||
On Thu, May 06, 1999 at 06:27:05PM +0200, Knut Bueltemann wrote:
> >
> > ID: 1379
> > Updated by: eschmid
> > Reported By: bueltemann@adinfo.de
> > Status: Closed
> > Bug Type: Performance problem
> > Assigned To:
> > Comments:
> >
> > I cannot see your problem with performance. Install your database server
> >
> > local and make use of your Unix socket's.
> >
> > -Egon
>
> As I added:
> omitting the pg_close()-statement, and the page is fully there!
> Seems to me the thread with the db_connection terminated before PHP3 has
> read all data.
>
> As I said this appears on a multi-processor-machine!
>
> -Knut
Well, Apache does not make use of threads and is normally not affected by SMP
issues. I really don't see the possibility of a race here which could lead to
problems in the PostgreSQL module. Did you see any segfaults in the log?
As I've pointed out in private email, I tend to blame Linux 2.0 SMP for this.
Testing on another SMP system or Linux 2.2 could help with hunting down this
"bug".
--
Regards,
Sascha Schumann |
Consultant | finger sas@schell.de
| for PGP public key
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net