| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Jan van der Weijde <Jan(dot)van(dot)der(dot)Weijde(at)attachmate(dot)com> |
| Cc: | Alban Hertroys <alban(at)magproductions(dot)nl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance with very large tables |
| Date: | 2007-01-15 12:49:16 |
| Message-ID: | 45AB784C.2020306@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jan van der Weijde wrote:
> That is exactly the problem I think. However I do not deliberately
> retrieve the entire table. I use the default settings of the PostgreSQL
> installation and just execute a simple SELECT * FROM table.
> I am using a separate client and server (both XP in the test
> environment), but that should not make much difference.
> I would expect that the default behavior of PostgreSQL should be such
> that without LIMIT, a SELECT returns records immediately.
No it doesn't. You've asked for all the records, so it assumes you want
all the records. If you want a few at a time, use a cursor.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan van der Weijde | 2007-01-15 12:54:15 | Re: Performance with very large tables |
| Previous Message | Shoaib Mir | 2007-01-15 12:48:45 | Re: Performance with very large tables |