pg.ddx.io pgsql-php@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Robby Russell <rrussell@commandprompt.com>
To: A Palmblad <adampalmblad@yahoo.ca>
Cc: pgsql-php@postgresql.org
Subject: Re: PHP memory usage
Date: Wed, 02 Jun 2004 13:17:51 -0700
Message-ID: <40BE35EF.8030003@commandprompt.com> (raw)
In-Reply-To: <005501c44755$5a851580$97019696@AERS04>
References: <005501c44755$5a851580$97019696@AERS04>
A Palmblad typed this on 05/31/2004 02:22 PM:
> We've been running into some issues with PHP and Postgres, and memory usage.
> On a dual athlon 64, w/ 4 gigs of RAM, PHP 4.3.6, and Postgres 7.4.2 I've
> seen our server start to crawl after some queries returning very large
> result sets. Although large result sets aren't exactly what we want to be
> dealing with, I really want to avoid a situation where a user could disrupt
> our server with certain options to some searches.
>
> I did a quick commandline test, and it looks like PHP starts to eat memory
> during its call to pg_query. By eat memory, I mean use memory well in
> excess of php.ini's memory_limit of 8 megs. (I stop it around 90% of
> available memory usage) Is this acceptable behaviour, or should I report it
> to PHP as a bug? If not, are my only solutions to wrap my selects in
> cursors and/or to use limit?
>
> -Adam Palmblad
>
I am going to take a quick guess and suggest that test those queries in
psql itself. You might be running into some issues with your queries.
Test your queries with psql, EXPLAIN.
\h EXPLAIN
-Robby
--
Robby Russell, | Sr. Administrator / Lead Programmer
Command Prompt, Inc. | http://www.commandprompt.com
rrussell@commandprompt.com | Telephone: (503) 667.4564
view thread (9+ messages) latest in thread
Message-ID: <40BE35EF.8030003@commandprompt.com> Permalink: ../40BE35EF.8030003@commandprompt.com/ Also on: postgresql.org/message-id/40BE35EF.8030003@commandprompt.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: rrussell@commandprompt.com, adampalmblad@yahoo.ca Subject: Re: PHP memory usage In-Reply-To: <40BE35EF.8030003@commandprompt.com> References: <005501c44755$5a851580$97019696@AERS04> <40BE35EF.8030003@commandprompt.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