Re: is there a way to firmly cap postgres worker memory consumption?

Steve Kehlet <steve.kehlet@gmail.com> writes:
>> Did you either profiled or debugged it to see what is going on?

> I would love to learn more about how to do this, to get to the bottom of
> the memory usage. I can google around, or can you suggest any reads?

Once you've got a ulimit in place so that malloc eventually fails with
ENOMEM, the backend process should print a memory context dump on stderr
when it hits that.  Make sure your logging setup captures the process
stderr someplace (logging_collector works for this, syslog does not).
Post the dump here when you've got it.

            regards, tom lane