| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bertrand Petit <pgsql(at)phoe(dot)frmug(dot)org> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: 7.4 beta 1 getting out of swap |
| Date: | 2003-08-14 15:18:42 |
| Message-ID: | 1578.1060874322@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Bertrand Petit <pgsql(at)phoe(dot)frmug(dot)org> writes:
> On Thu, Aug 14, 2003 at 07:45:46AM -0400, Tom Lane wrote:
>> Please show us the memory context size info that the backend dumps to
>> stderr when it reports "out of memory".
> Here it is:
> ExecutorState: 4556232 total in 46 blocks; 3183264 free (8303 chunks); 1372968 used
That seems a bit large, but I'm not sure if it's really to worry about.
> ExecutorState: 528474112 total in 72 blocks; 760 free (1 chunks); 528473352 used
Okay, you definitely must have a memory leak in query execution.
Could you provide enough info to let someone else reproduce it? We
don't need your data, but a schema dump (pg_dump -s) would be nice
to avoid trying to guess what causes it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlos Guzman Alvarez | 2003-08-14 15:46:05 | SSL Connection / Windows + Cygwin + PostgreSQL 7.4 Beta 1 question |
| Previous Message | Bertrand Petit | 2003-08-14 14:53:11 | Re: 7.4 beta 1 getting out of swap |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy M. Guthrie | 2003-08-14 17:55:32 | Vacuum performance question |
| Previous Message | Jan Wieck | 2003-08-14 15:02:53 | Re: [SQL] EXTERNAL storage and substring on long strings |