Carlos Henrique Reimer <carlos.reimer@xxxxxxxxxxxxx> writes: > That is what I got from gdb: > ExecutorState: 11586756656 total in 1391 blocks; 4938408 free (6 > chunks); 11581818248 used So, query-lifespan memory leak. After poking at this for a bit, I think the problem has nothing to do with joins; more likely it's because you are returning a composite column: select wm_nfsp from "5611_isarq".wm_nfsp ... I found out that record_out() leaks sizable amounts of memory, which won't be recovered till end of query. You could work around that by returning "select wm_nfsp.*" instead, but if you really want the result in composite-column notation, I'd suggest applying this patch: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c027d84c81d5e07e58cd25ea38805d6f1ae4dfcd regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
