On Fri, Aug 28, 2009 at 5:18 AM, Greg Smith<gsm...@gregsmith.com> wrote: > On Fri, 28 Aug 2009, Tom Lane wrote: > >> MemoryContextStats() might help. It just dumps the info to stderr >> though. > > Which means it ends up in the database log files in the common configuration > where where the database's stderr is redirected to there. I even script > running this regularly against stuff I'm suspicious of, using something like > this passed the PID of the process I want to watch: > > #!/bin/bash > gdb -p $1 <<EOF > p MemoryContextStats(TopMemoryContext) > detach > quit > EOF > > -- > * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD >
Is there another way to get it in the source code? I need to control the size of a memory context on the fly and take some actions when the used memory exceeds a defined size. Thanks Adriano -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
