Re: Manipulating complex types as non-contiguous structures in-memory

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Martijn van Oosterhout <kleptog@svana.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2015-02-14T17:53:58Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Sat, Feb 14, 2015 at 10:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Martijn van Oosterhout <kleptog@svana.org> writes:
>>> The words that sprung to mind for me were: packed/unpacked.

>> Trouble is that we're already using "packed" with a specific connotation
>> in that same area of the code, namely for short-header varlena values.
>> (See pg_detoast_datum_packed() etc.)  So I don't think this will work.
>> But maybe a different adjective?

> expanded?

That seems to work from the standpoint of not conflicting with other
nearby usages in our code, and it's got the right semantics I think.

Any other suggestions out there?  Otherwise I'll probably go with this.

			regards, tom lane


Commits

  1. Use fast path in plpgsql's RETURN/RETURN NEXT in more cases.

  2. Add support for multiple kinds of external toast datums.