| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Clarification reqeusted for "select * from a huge table" |
| Date: | 2007-11-12 12:31:13 |
| Message-ID: | 47384791.5070904@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gokulakannan Somasundaram wrote:
> I had a chance to test one of the real world cases with Oracle and
> PostgreSQL. Create a Table with 10 million rows (i worked on a 1GB RAM
> machine) both in oracle and Postgresql. Just write a JDBC program for
> a 'select *' on that table. With PostgreSQL as backend, java crashes
> saying that it has met 'Out Of Memory'. With Oracle it doesn't.
> Postgres tried to send all the results back to the client at one
> shot, whereas in Oracle it works like a Cursor. Is this issue already
> well known among hackers community? If known, why is it designed this
> way?
http://jdbc.postgresql.org/documentation/head/query.html#query-with-cursor
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokulakannan Somasundaram | 2007-11-12 12:35:12 | Re: Clarification reqeusted for "select * from a huge table" |
| Previous Message | Trevor Talbot | 2007-11-12 12:00:04 | Re: 8.2.3: Server crashes on Windows using Eclipse/Junit |