ID: 33587 Updated by: [EMAIL PROTECTED] Reported By: vda at ilport dot com dot ua -Status: Open +Status: Bogus Bug Type: PostgreSQL related Operating System: Linux PHP Version: 4.3.10 New Comment:
PG has mailing list for reporting and discussing PG bugs and you can use it for reporting *their* issues directly to *them*. See http://www.postgresql.org/community/lists/ This is not a support forum or a free bug tracking system that you can use to report any bugs you find in someone's libs. This system is only for bugs in PHP itself. As for your issue: this is not PHP problem -> bogus. Previous Comments: ------------------------------------------------------------------------ [2005-07-06 14:04:35] vda at ilport dot com dot ua Which part of below text you do not understand? >Apparently PostgreSQL team does not have bugzilla. >I reported the issue to PostgreSQL team also >using http://www.postgresql.org/support/submitbug, >repeating bug report and also gave then URL >to this page. ------------------------------------------------------------------------ [2005-07-06 14:01:28] vda at ilport dot com dot ua This is the script which shows the issue nicely. It reads and immediately discards all rows (was written as a benchmark "PG versus Oracle"). Table has 200Mb of data in it. Apache's memory usage was outright silly (~250Mb). <? $db = pg_connect("host=172.17.13.22 port=5432 dbname=traffic user=postgres"); /* php bug? sweels enormously while executing this: */ $result = pg_query($db, "SELECT * FROM payment"); $count = 0; while (pg_fetch_row($result)) { $count++; if (($count % 1000)==0) echo "$count<br>"; } echo "Done, count=$count"; ?> ------------------------------------------------------------------------ [2005-07-06 14:00:02] [EMAIL PROTECTED] Yes. PostgreSQL bugs do not belong here, report them to the PG developers instead. ------------------------------------------------------------------------ [2005-07-06 13:58:07] vda at ilport dot com dot ua I've seen several vague bug reports here "PHP eats lots of mem with PostgreSQL" but none was researched in any depth. I thought I can spend at least ten minutes at it. Also I wanted to have an URL where this bug is reported. Apparently PostgreSQL team does not have bugzilla. I reported the issue to PostgreSQL team also using http://www.postgresql.org/support/submitbug, repeating bug report and also gave then URL to this page. Did I do something wrong? ------------------------------------------------------------------------ [2005-07-06 13:39:29] [EMAIL PROTECTED] >I think this is a problem with PostgreSQL client libs. Please explain: you think that this is a problem with PG client libs and you're reporting it in PHP bug system? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/33587 -- Edit this bug report at http://bugs.php.net/?id=33587&edit=1
