Re: Query memory usage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tom Duffey <tduffey(at)trillitech(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Query memory usage
Date: 2010-05-15 21:51:13
Message-ID: 18358.1273960273@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Duffey <tduffey(at)trillitech(dot)com> writes:
> I have a table with several hundred million rows of timestamped
> values. Using pg_dump we are able to dump the entire table to disk no
> problem. However, I would like to retrieve a large subset of data
> from this table using something like:

> COPY (SELECT * FROM history WHERE timestamp > '2009-01-01') TO STDOUT;

> Executing this query causes our server to consume all available swap
> and crash.

What's being done on the client side with the data? AFAIK that
operation really shouldn't consume a lot of memory on the server side.
It would help if you'd be more specific about which process is consuming
swap space.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Yang Zhang 2010-05-15 22:40:29 Bizarre problem: Python stored procedure using protocol buffers not working
Previous Message Tom Lane 2010-05-15 21:47:39 Re: how to get Point * from datum =heap_getattr(....)?