Paul Smith <paulsmith@pobox.com> writes:
> We have a query that's producing an "out of memory" error
> consistently. The detail of the error message is "Failed on request of
> size 16." We have 16 GB of RAM in our database server running 32-bit
> Debian lenny. Here's the query:
> ...
> ExecutorState: 460390096 total in 431 blocks; 8400 free (2
> chunks); 460381696 used
Clearly a memory leak, but it's not so clear exactly what's causing it.
What's that intersects() function? Can you put together a
self-contained test case?
regards, tom lane
