Re: [BUGS] BUG #1756: PQexec eats huge amounts of memory

2005-07-18 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> writes: > Are you saying that if I execute a statement like: > select * from "TableWithHundredsOfMillionsOfRows" > that the entire table will be copied to a result set before returning > the first row? libpq does things that way, yes. > Is this result set bu

Re: [BUGS] BUG #1756: PQexec eats huge amounts of memory

2005-07-18 Thread Kris Jurka
On Mon, 18 Jul 2005, Kevin Grittner wrote: > Are you saying that if I execute a statement like: > select * from "TableWithHundredsOfMillionsOfRows" > that the entire table will be copied to a result set before returning > the first row? Is this result set built in RAM on the server side? > >

[BUGS] BUG #1774: ecpg preprocessor produces a wrong varchar struct

2005-07-18 Thread Dirk Jagdmann
The following bug has been logged online: Bug reference: 1774 Logged by: Dirk Jagdmann Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: i686 Linux 2.6 Description:ecpg preprocessor produces a wrong varchar struct Details: The ecpg preproc

Re: [BUGS] BUG #1756: PQexec eats huge amounts of memory

2005-07-18 Thread Kevin Grittner
Are you saying that if I execute a statement like: select * from "TableWithHundredsOfMillionsOfRows" that the entire table will be copied to a result set before returning the first row? Is this result set built in RAM on the server side? I am interested primarily in the behavior under JDBC,