On 11/26/2014 05:26 PM, Peter Geoghegan wrote:
On Wed, Nov 26, 2014 at 2:00 PM, Andrew Dunstan <and...@dunslane.net> wrote:
The client's question is whether this is not a bug. It certainly seems like
it should be possible to plan a query without chewing up this much memory,
or at least to be able to limit the amount of memory that can be grabbed
during planning. Going from humming along happily to OOM conditions all
through running "explain <somequery>" is not very friendly.
Have you tried this with a "#define SHOW_MEMORY_STATS" build, or
otherwise rigged Postgres to call MemoryContextStats() at interesting
times?
No, but I can. Good idea, thanks.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
