Re: Detection of nested function calls - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Detection of nested function calls
Date
Msg-id CA+TgmoaQdd6DyY9HJxr7HYFDwtTYKaS1piZCDnBTg2Bw1r_i3g@mail.gmail.com
Whole thread Raw
In response to Re: Detection of nested function calls  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Detection of nested function calls  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Oct 28, 2013 at 11:12 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The idea I'm thinking about at the moment is that toast tokens of this
> sort might each contain a function pointer to the required flattening
> function.  This avoids an expensive catalog lookup when flattening is
> needed.  We'd never accept such a thing for data destined for disk;
> but since the whole point here is that such data lives only in memory,
> I can't see anything wrong with including a function pointer in it.

This might be OK, but it bloats the in-memory representation.  For
small data types like numeric that might well be significant.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: OSX doesn't accept identical source/target for strcpy() anymore
Next
From: Tom Lane
Date:
Subject: Re: RULE regression test fragility?