Re: Analyze on large changes... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Analyze on large changes...
Date
Msg-id 6182.1023852152@sss.pgh.pa.us
Whole thread Raw
In response to Re: Analyze on large changes...  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Analyze on large changes...  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> Seems like a pretty serious (not to say fatal) objection to me.  Surely
>> you can fix that.

> OK, suggestions.  I know CommandCounterIncrement will not help.  Should
> I do more pfree'ing?

No, retail pfree'ing is not a maintainable solution.  I was thinking
more along the lines of a MemoryContextResetAndDeleteChildren() on
whatever the active context is.  If that doesn't work straight off,
you might have to create a new working context and switch into it
before calling the analyze subroutine --- then deleting that context
would do the trick.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Schemas and template1
Next
From: Tom Lane
Date:
Subject: Re: Schemas and template1