| From: | Erik Jones <erik(at)myemma(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | henk de wit <henk53602(at)hotmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Huge amount of memory consumed during transaction |
| Date: | 2007-10-11 16:51:08 |
| Message-ID: | 69723004-A93C-41DE-BC69-57ABFAB059C2@myemma.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Oct 11, 2007, at 9:51 AM, Tom Lane wrote:
> henk de wit <henk53602(at)hotmail(dot)com> writes:
>> ERROR: out of memory
>> DETAIL: Failed on request of size 4194304.
>
> This error should have produced a map of per-context memory use in the
> postmaster log. Please show us that.
>
> regards, tom lane
Tom, are there any docs anywhere that explain how to interpret those
per-context memory dumps? For example, when I see an autovacuum
context listed is it safe to assume that the error came from an
autovac operation, etc.?
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-10-11 17:28:51 | Re: Performance problems with prepared statements |
| Previous Message | Benjamin Arai | 2007-10-11 16:12:20 | Re: [PERFORM] Slow TSearch2 performance for table with 1 million documents. |