"Matt Magoffin" <postgresql.org@xxxxxxx> writes: > Later, I added a large set of plpgsql trigger functions that operate on > that new xml column data, using the xpath() function to extract bits of > XML and populate them into normal tables. The server has been running in > this fashion for many months now, and there is a noticeable difference in > how Postgres is using memory now, in that over time it's non-shared memory > use is climbing higher and higher. Right now I'm tracking this from data > captured by Munin on the system. The memory creep is very slight, but over > many months is easy to discern. Ugh. Sounds like "small memory leak inside libxml2" --- probably not going to be easy to find. Can you put together a self-contained test case? regards, tom lane
