On Thu, Aug 25, 2016 at 12:34 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Theron Luhn <theron@luhn.com> writes: >> It would be worth using plain old top to watch this process. We have >> enough experience with that to be pretty sure how to interpret its >> numbers: "RES minus SHR" is the value to be worried about.
(when the process has reached an idle but bloated state) and seeing what gets printed to the process's stderr. (You need to have launched the postmaster with its stderr directed to a file, not to /dev/null.) That would provide a better clue about what's eating space.