Tom - that make sense... and fits the timeline of when the instability may have been introduced.
I use soft references in java to track these relationships. When the GC needs memory it will collect
objects referenced by soft references so I need to have this exception caught where my caches may get cleaned.
When the system is under load as it would be in this case, there references would be cleaned causing a large
number of exceptions in the pgplsql, subsequently causing the leak... hence the swift downward spiral.
The previous version of these routines used selects but due to volume of selects, performance suffered quite
a bit. I dont think I could revert now for production use... closing the connection maybe the workaround for
us for this release IF this is in fact what the problem is. Unfortunatly, I use the catch in about 20 similar
routines to reset sequences etc.... this may be painful :(
I will modify the routine to help isolate the problem. stay tuned.
BTW - the fix you mentioned .... is that targeted for 8.2? Is there a timeline for 8.2?
On Thursday 15 June 2006 12:44, Tom Lane wrote:
> "jody brownell" <jody.brownell@Q1Labs.com> writes:
> > BEGIN
> > INSERT into attacker_target_link (attacker_id, target_id) values (p_attacker, v_target);
> > v_returns_size := v_returns_size + 1;
> > v_returns[v_returns_size] := v_target;
>
> > EXCEPTION WHEN unique_violation THEN
> > -- do nothing... app cache may be out of date.
> > END;
>
> Hmm. There is a known problem that plpgsql leaks some memory when
> catching an exception:
> http://archives.postgresql.org/pgsql-hackers/2006-02/msg00885.php
>
> So if your problem case involves a whole lot of duplicates then that
> could explain the initial bloat. However, AFAIK that leakage is in
> a transaction-local memory context, so the space ought to be freed at
> transaction end. And Linux's malloc does know about giving space back
> to the kernel (unlike some platforms). So I'm not sure why you're
> seeing persistent bloat.
>
> Can you rewrite the function to not use an EXCEPTION block (perhaps
> a separate SELECT probe for each row --- note this won't be reliable
> if there are concurrent processes making insertions)? If so, does
> that fix the problem?
>
> regards, tom lane
>
>
>
