On Thu, Nov 25, 2010 at 05:28, Darryl Pye <darrylpye@hotmail.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05767
> Logged by: =A0 =A0 =A0 =A0 =A0Darryl Pye
> Email address: =A0 =A0 =A0darrylpye@hotmail.com
> PostgreSQL version: 9.01
> Operating system: =A0 Windows Server =A02008
> Description: =A0 =A0 =A0 =A0Memory Leak
> Details:
>
> A single postgres =A0process =A0appears to be constantly growing in memor=
y usage
> =A0until it reaches 100% of memory on the machine.
>
> I have rebooted the server and the problem goes away but then =A0a single
> postgres.exe process continues to =A0eat memory until it uses all availab=
le
> ram then i have to restart again.
>
> Machine has 4 gig of ram available.
> I am able to watch the process grow constantly at approximately =A08kb ev=
ery
> second.
>
> Until it reaches =A04gig.
>
> I have made the following configuration changes from default
> shared_buffers =3D 1GB
> wal_buffers =3D 1MB
> effective_cache_size =3D 2GB
What are your work_mem and maintenance_work_mem settings?
And which of the postgres processes is it, and what's it doing? You
can use Process Explorer to look at the process, and find a handle
called something starting with "pgident" - that one will contain a
description of the process, just like the title does on Unix. Or you
can look up the process id in the pg_stat_activity view to identify
it.
--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/