Re: [HACKERS] tupdesc reference is not owned by resource owner Portal

Tom Lane wrote: Stefan Kaltenbrunner [EMAIL PROTECTED] writes: Tom Lane wrote: I think the proper fix is probably to establish a new eval_context when we enter an EXCEPTION block, and destroy it again on the way out. Slightly annoying, but probably small next to the other overhead of a

Re: [HACKERS] tupdesc reference is not owned by resource owner Portal

Stefan Kaltenbrunner [EMAIL PROTECTED] writes: Tom Lane wrote: I think the proper fix is probably to establish a new eval_context when we enter an EXCEPTION block, and destroy it again on the way out. Slightly annoying, but probably small next to the other overhead of a subtransaction.

[HACKERS] tupdesc reference is not owned by resource owner Portal issue in 8.2 and -HEAD

The following testcase(extracted from a much much larger production code sample) results in WARNING: TupleDesc reference leak: TupleDesc 0xb3573b88 (2249,1) still referenced CONTEXT: PL/pgSQL function foo line 4 at block variables initialization ERROR: tupdesc reference 0xb3573b88 is not

Re: [HACKERS] tupdesc reference is not owned by resource owner Portal issue in 8.2 and -HEAD

Stefan Kaltenbrunner [EMAIL PROTECTED] writes: The following testcase(extracted from a much much larger production code sample) results in WARNING: TupleDesc reference leak: TupleDesc 0xb3573b88 (2249,1) still referenced CONTEXT: PL/pgSQL function foo line 4 at block variables

Re: [HACKERS] tupdesc reference is not owned by resource owner Portal

Tom Lane wrote: Stefan Kaltenbrunner [EMAIL PROTECTED] writes: The following testcase(extracted from a much much larger production code sample) results in WARNING: TupleDesc reference leak: TupleDesc 0xb3573b88 (2249,1) still referenced CONTEXT: PL/pgSQL function foo line 4 at block