Re: Composite Datums containing toasted fields are a bad idea(?)

On 04/25/2014 02:40 AM, Tom Lane wrote:
> * The patch changes HeapTupleGetDatum from a simple inline macro into
> a function call.  This means that third-party extensions will not get
> protection against creation of toast-pointer-containing composite Datums
> until they recompile.

One consequence of that is that an extension compiled with headers from 
new minor version won't work with binaries from an older minor version. 
Packagers beware.

- Heikki