From: | Shane Ambler <pgsql(at)007Marketing(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 15:10:06 |
Message-ID: | 45AB994E.8080500@007Marketing.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
You will want to increase the default settings and let PostgreSQL use as
much RAM as you have - especially when retrieving a large dataset.
Some good points of reference is -
http://www.powerpostgresql.com/Downloads/annotated_conf_80.html
http://www.varlena.com/GeneralBits/Tidbits/perf.html
http://www.powerpostgresql.com/PerfList
> 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.
>
> Thank you,
> Jan
--
Shane Ambler
pgSQL(at)007Marketing(dot)com
Get Sheeky @ http://Sheeky.Biz
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Kmetec | 2007-01-15 15:15:08 | Unpredicatable behavior of volatile functions used in cursors |
Previous Message | Aleksander Kmetec | 2007-01-15 14:40:46 | Re: index type for indexing long texts |