Re: Alignment padding bytes in arrays vs the planner

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Alignment padding bytes in arrays vs the planner
Date: 2011-05-24 18:17:02
Message-ID: BANLkTi=a7N3T3EBac9O=g5hmQMELU_Ppyw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 24, 2011 at 2:11 PM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>> OK, I can't see what's broken.  Help?
>
> QTN2QT() allocates memory for a TSQuery using palloc().  TSQuery contains an
> array of QueryItem, which contains three bytes of padding between its first and
> second members.  Those bytes don't get initialized, so we have unpredictable
> content in the resulting datum.

OK, so I guess this needs to be applied and back-patched to 8.3, then.
8.2 doesn't have this code.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2011-05-24 18:17:59 Re: Domains versus polymorphic functions, redux
Previous Message Tom Lane 2011-05-24 18:13:40 Re: "errno" not set in case of "libm" functions (HPUX)