| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | vda(at)ilport(dot)com(dot)ua, tgl(at)sss(dot)pgh(dot)pa(dot)us, alvherre(at)alvh(dot)no-ip(dot)org, pierce(at)hogranch(dot)com, pgsql-bugs(at)postgresql(dot)org, neilc(at)samurai(dot)com |
| Subject: | Re: BUG #1756: PQexec eats huge amounts of memory |
| Date: | 2005-07-18 21:08:04 |
| Message-ID: | Pine.BSO.4.56.0507181606360.5724@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
>
> I am interested primarily in the behavior under JDBC, although psql is
> also significant.
http://jdbc.postgresql.org/documentation/80/query.html#query-with-cursor
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcus Raphelt | 2005-07-19 13:17:42 | BUG #1775: UTF8 to ISO does not convert the german "sharp s" (ß ) |
| Previous Message | Tom Lane | 2005-07-18 20:25:40 | Re: BUG #1756: PQexec eats huge amounts of memory |