Re: Manipulating complex types as non-contiguous structures in-memory - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Manipulating complex types as non-contiguous structures in-memory
Date
Msg-id 20150213080454.GA24787@svana.org
Whole thread Raw
In response to Re: Manipulating complex types as non-contiguous structures in-memory  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Manipulating complex types as non-contiguous structures in-memory  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: Manipulating complex types as non-contiguous structures in-memory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Feb 12, 2015 at 08:52:56AM -0500, Robert Haas wrote:
> > BTW, I'm not all that thrilled with the "deserialized object" terminology.
> > I found myself repeatedly tripping up on which form was serialized and
> > which de-.  If anyone's got a better naming idea I'm willing to adopt it.
>
> My first thought is that we should form some kind of TOAST-like
> backronym, like Serialization Avoidance Loading and Access Device
> (SALAD) or Break-up, Read, Edit, Assemble, and Deposit (BREAD).  I
> don't think there is anything per se wrong with the terms
> serialization and deserialization; indeed, I used the same ones in the
> parallel-mode stuff.  But they are fairly general terms, so it might
> be nice to have something more specific that applies just to this
> particular usage.

The words that sprung to mind for me were: packed/unpacked.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> He who writes carelessly confesses thereby at the very outset that he does
> not attach much importance to his own thoughts.  -- Arthur Schopenhauer

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgaudit - an auditing extension for PostgreSQL
Next
From: Michael Paquier
Date:
Subject: Re: Patch to support SEMI and ANTI join removal