Kristofer Munn <kmunn@munn.com> writes:
> I've created a sample case that reproduces the error that I will attach
> with this message. Basically, I create a 50 column temp table (with no
> rows in it) and then run updates on each column in succession. The
> backend gets large pretty quick - I'm seeing about 12Megs after running
> the enclosed script which does an update on all 50 columns 3 times (150
> updates).
I confirm the leak in 6.5.* --- but I see no leak in current sources.
regards, tom lane
