> 9.3.which? We do fix memory leaks from time to time ...
9.3.14
> If it's not an outright leak, it's probably consumption of cache space.
> We cache stuff that we've read from system catalogs, so sessions that
> touch lots of tables (like thousands) can grow due to that. Another
> possible source of large cache consumption is calling lots-and-lots of
> plpgsql functions.
I have a reasonable number of tables (around 50) and very few plpgsql functions.
> If the same query, repeated over and over, causes memory to continue
> to grow, I'd call it a leak (ie bug). If repeat executions consume
> no additional memory then it's probably intentional caching behavior.
So kind of a combination of the two: Memory usage increases up to a certain point but then plateaus. So... cache? It's ~100MB increase, though, which seems an excessive amount. What could be taking up that much cache?