Till Kirchner <till.kirchner@xxxxxxxxxxx> writes: > I get an out of memory problem I don't understand. It's pretty clear that something is leaking memory in the per-query context: > ExecutorState: 1833967692 total in 230 blocks; 9008 free (3 > chunks); 1833958684 used There doesn't seem to be anything in your query that is known to cause that sort of thing, so I'm guessing that the leak is being caused by the postgis functions you're using. You might ask about this on the postgis lists. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
