Tom Lane <tgl@sss.pgh.pa.us> writes:
> 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.
That's a good reason to get them into a shorter memory context, but
which? per transaction maybe? shorter?
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support