Re: postgres.exe mem usage in task manager

> I noticed a curious thing: the task manager does not seem to
> account for shared memory (memory mapped files) in the memory
> usage, making it appear that that the backends are allocating
> more memory than they really are.

Have you checked the "Virtual Memory Size" column? (Not enabled by
default)


> I confirmed that the total allocation for all the backends
> was reasonable by checking the system commit but if you add
> up allocations for each backend it appears much higher.

If the above does not work, check with the performance monitor...

Microsoft has changed the way task manager reports memory usage between
pretty much every windows version (particularly the summary fields)...
Which version are you on?


> checkpointing on win32 seems to run very fast...much faster
> than I'm used to, but this may be do to improvements in the
> bgwriter.  It cleans the clock of the Interix port (MS's own
> unix runtime) by at least 15% on insert heavy situations.
> Overall, I am just blown away on how well the whole thing
> works compared to just a few weeks ago.

Checkpointing is a no-op on win32. sync() does nothing. (OK, not quite
no-op, it writes a checkpoint record.. But without checkpointing, that
is actually incorrect).
This is the item at the very top of the TODO list on Bruces win32 status
page (http://momjian.postgresql.org/main/writings/pgsql/win32.html). Tom
has offered to change how sync() is handled in general, which is pretty
much needed before we can fix this on Win32.


//Magnus