Re: Memory leaks in record_out and record_send - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory leaks in record_out and record_send
Date
Msg-id 19966.1352824077@sss.pgh.pa.us
Whole thread Raw
In response to Re: Memory leaks in record_out and record_send  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Memory leaks in record_out and record_send  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> Thoughts?

> I've been using textin(record_out(NEW)) in generic partitioning
> triggers, and you can find examples of that trick in the wiki, so I
> think we have users of that in the field.

I think explicit calls like that actually wouldn't be a problem,
since they'd be run in a per-tuple context anyway.  The cases that
are problematic are hard-coded I/O function calls.  I'm worried
about the ones like, say, plpgsql's built-in conversion operations.
We could probably fix printtup's usage with some confidence, but
there are a lot of other ones.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Memory leaks in record_out and record_send
Next
From: Robert Haas
Date:
Subject: Re: Index only scans wiki page