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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Denis Vlasenko <vda(at)ilport(dot)com(dot)ua>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>,John R Pierce <pierce(at)hogranch(dot)com>, 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-14 12:38:27
Message-ID: 13620.1121344707@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Denis Vlasenko <vda(at)ilport(dot)com(dot)ua> writes:
> On Wednesday 13 July 2005 17:43, Tom Lane wrote:
>> The reason it cannot be done transparently is that you would lose the
>> guarantee that a query either succeeds or fails: it would be entirely
>> possible to return some rows to the application and only later get a
>> failure.

> What failures are likely?

Consider
	select x, 1/x from foo;

where x is zero in the 10,000'th row ...

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Nigel KukardDate: 2005-07-14 12:41:39
Subject: BUG #1769: pg_dumpall fails to run
Previous:From: Stefan MiefertDate: 2005-07-14 10:40:16
Subject: [postgres] Datumsfeld leer lassen

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