From: | Suzuki Hironobu <hironobu(at)interdb(dot)jp> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql client memory usage |
Date: | 2013-09-06 13:11:03 |
Message-ID: | 5229D467.8010205@interdb.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
(13/09/06 21:06), Tim Kane wrote:
> Hi all,
>
> I have a fairly simple query, running on a particularly large table. For
> illustration:
>
> echo "select * from really_big_table;" | psql my_database > /dev/null
>
>
> When I monitor the memory usage of the psql session, it continually grows.
> In fact, for this particularly large table it grows to the point of
> consuming all swap, before the OOM killer takes steps to resolve it.
> Clearly, this isn't what I'd like to happen.
>
>
> My settings are:
> Postgresql 9.1.9
> work_mem = 256MB
> effective_cache_size = 12GB
> shared_buffers = 6GB
>
> I have 24GB physical ram to play with.
>
This is a client side problem (not server size).
See the description of FETCH_COUNT, please.
http://www.postgresql.org/docs/9.2/static/app-psql.html
echo "select * from really_big_table;" | psql --variable=FETCH_COUNT=100
my_database > /dev/null
Regards,
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-09-06 13:16:42 | Re: How to check if any WAL file is missing in archive folder |
Previous Message | Michael Paquier | 2013-09-06 13:08:46 | Re: Old record migration to another table made the db slower |