Postgres Pro
Downloads
Home   >   mailing lists

Re: memory explosion on planning complex query - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: memory explosion on planning complex query
Date
Msg-id CAM3SWZQ9BcTc6n4tAY5Vdx+wS5Mo7DweLXW4y4CQWaRkNtESuw@mail.gmail.com
Whole thread Raw
In response to memory explosion on planning complex query  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: memory explosion on planning complex query  (Tomas Vondra <tv@fuzzy.cz>)
Re: memory explosion on planning complex query  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Tree view 
On Wed, Nov 26, 2014 at 2:00 PM, Andrew Dunstan <andrew@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?

-- 
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: memory explosion on planning complex query
Next
From: Tomas Vondra
Date:
Subject: Re: memory explosion on planning complex query