| From: | Douglas McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | Sven Willenberger <sven(at)dmv(dot)com> |
| Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org>, Francisco Reyes <lists(at)stringsutils(dot)com> |
| Subject: | Re: out of memory for query result |
| Date: | 2006-05-03 17:16:52 |
| Message-ID: | 87zmhz9gfv.fsf@suzuka.mcnaught.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sven Willenberger <sven(at)dmv(dot)com> writes:
> On Sat, 2006-04-22 at 15:08 -0400, Tom Lane wrote:
>> Francisco Reyes <lists(at)stringsutils(dot)com> writes:
>> > What resource do I need to increase to avoid the error above?
>>
>> Process memory allowed to the client; this is not a server-side error.
>>
>
> I am experiencing an "out of memory" situation as well on large query
> results, even with allowing 2G process memory to the client:
The server settings don't have anything to do with this problem. The
client is trying to read the entire result set into memory before it
writes it out (that's just the way it works). You can do it in
smaller chunks by using a cursor with DECLARE and FETCH.
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2006-05-03 17:29:10 | Re: database size grows (even after vacuum (full and analyze)).... |
| Previous Message | Joao Miguel Ferreira | 2006-05-03 17:15:37 | Re: database size grows (even after vacuum (full and analyze)).... |