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

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Composite Datums containing toasted fields are a bad idea(?)
Date: 2014-04-25 06:28:55
Message-ID: 535A00A7.4060501@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2014-04-25 12:43:23 Re: Json(b) extension
Previous Message Tom Lane 2014-04-25 02:21:17 Re: review: Non-recursive processing of AND/OR lists