Skip site navigation (1) Skip section navigation (2)

Re: BUG #1756: PQexec eats huge amounts of memory

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Denis Vlasenko <vda(at)ilport(dot)com(dot)ua>
Cc: Neil Conway <neilc(at)samurai(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1756: PQexec eats huge amounts of memory
Date: 2005-07-07 15:09:25
Message-ID: 20050707150925.GD7157@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, Jul 07, 2005 at 09:51:54AM +0300, Denis Vlasenko wrote:

> I wanted to show colleagues which are Oracle admins that peak
> data fetch rate of PostgreSQL is way better than Oracle one.
> 
> While it turned out to be true (Oracle+WinNT = 2kb TCP output buffer,
> ~1Mb/s over 100Mbit; PostgreSQL+Linux = 8kb buffer, ~2.6Mb/s),
> I was ridiculed instead when my php script failed miserably,
> crashing Apache with OOM condition, while alanogous script for Oracle
> ran to completion just fine.

You should have tested the script before showing off :-)  You may want
to convert it to manually use a cursor, at least the Postgres version.
That would alleviate the memory problem.

-- 
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"Some men are heterosexual, and some are bisexual, and some
men don't think about sex at all... they become lawyers" (Woody Allen)

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-07-07 15:12:46
Subject: Re: BUG #1757: timestamp 'epoch' is not absolute
Previous:From: Michael FuhrDate: 2005-07-07 15:08:36
Subject: Re: Sun inline assembler ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group