| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: memory explosion on planning complex query |
| Date: | 2014-11-26 22:41:55 |
| Message-ID: | 54765733.8090309@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/26/2014 05:26 PM, Peter Geoghegan wrote:
> On Wed, Nov 26, 2014 at 2:00 PM, Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-11-26 22:48:43 | Re: bug in json_to_record with arrays |
| Previous Message | Antonin Houska | 2014-11-26 22:41:24 | Re: memory explosion on planning complex query |