Alvaro Herrera <alvhe...@commandprompt.com> writes: > Excerpts from Tom Lane's message of miÃ© oct 27 18:18:06 -0300 2010: >> I spent quite a bit of time trying to deal with the memory-leakage >> problem without adding still more bookkeeping overhead. It wasn't >> looking good, and then I had a sudden insight: if we see that the in-use >> flag is set, we can simply return FALSE from exec_eval_simple_expr.
> I tried the original test cases that were handed to me (quite different > from what I submitted here) and they are fixed also. Thanks. It'd be interesting to know if there's any noticeable slowdown on affected real-world cases. (Of course, if they invariably crashed before, there might not be a way to measure their previous speed...) regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers