Re: SerializeParamList vs machines with strict alignment

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, hlinnaka <hlinnaka@iki.fi>
Date: 2018-10-02T05:51:30Z
Lists: pgsql-hackers

Attachments

On Tue, Oct 2, 2018 at 10:07 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Amit Kapila <amit.kapila16@gmail.com> writes:
> > On Tue, Oct 2, 2018 at 9:38 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> (But it might be worth choosing slightly less
> >> generic object names, to avoid a conflict against other sub-tests
> >> later in that script.)
>
> > The function name and statement name seems okay to me.  How about
> > changing the table name to fooarr or arrtest?
>
> Up to you.
>

Okay, I have pushed the test case patch on HEAD.  Attached is the
code-fix patch, let's wait for a day so that we have all the results
which can help us to discuss the merits of this patch.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. MAXALIGN the target address where we store flattened value.

  2. Test passing expanded-value representations to workers.