"Oliver Elphick" <olly@lfix.co.uk> writes:
> Can someone advise, please, how to deal with this problem in 6.5.3?
My guess is that the cause is memory leaks during expression evaluation;
but without seeing the complete view definitions and underlying table
definitions, it's impossible to know what processing is being invoked
by this query...
regards, tom lane