Re: Composite Datums containing toasted fields are a bad idea(?) - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Composite Datums containing toasted fields are a bad idea(?)
Date
Msg-id 535A00A7.4060501@vmware.com
Whole thread Raw
In response to Re: Composite Datums containing toasted fields are a bad idea(?)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Composite Datums containing toasted fields are a bad idea(?)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: review: Non-recursive processing of AND/OR lists
Next
From: Dmitry Dolgov
Date:
Subject: Re: Json(b) extension