Skip site navigation (1) Skip section navigation (2)

Re: BUG #4996: postgres.exe memory consumption keeps going up

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: "WANGRUNGVICHAISRI, SHIVESH" <sbw(at)appsig(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up
Date: 2009-08-26 16:20:13
Message-ID: 407d949e0908260920u1711a6ebrfae52c05f15fb3af@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Wed, Aug 26, 2009 at 4:38 PM, Craig
Ringer<craig(at)postnewspapers(dot)com(dot)au> wrote:
> If it is in fact postgres.exe that crashes at some point, it'd also
> *REALLY* help to have a backtrace of the crash.

If Postgres crashes due to running out of memory it prints a memory
dump to its log which would (hopefully) make it clear where the memory
leak is. I don't know where to find Postgres logs on Windows but it
shouldn't be hard to find.

-- 
greg
http://mit.edu/~gsstark/resume.pdf

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2009-08-26 16:25:47
Subject: Re: 8.5 release timetable, again
Previous:From: Andrew DunstanDate: 2009-08-26 16:19:02
Subject: Re: pretty print viewdefs

pgsql-bugs by date

Next:From: John R PierceDate: 2009-08-26 16:34:17
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up
Previous:From: Tom LaneDate: 2009-08-26 15:40:04
Subject: Re: BUG #5011: Standby recovery unable to follow timeline change

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group