Re: Alignment padding bytes in arrays vs the planner - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Alignment padding bytes in arrays vs the planner
Date
Msg-id BANLkTi=a7N3T3EBac9O=g5hmQMELU_Ppyw@mail.gmail.com
Whole thread Raw
In response to Re: Alignment padding bytes in arrays vs the planner  (Noah Misch <noah@leadboat.com>)
Responses Re: Alignment padding bytes in arrays vs the planner  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, May 24, 2011 at 2:11 PM, Noah Misch <noah@leadboat.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: "errno" not set in case of "libm" functions (HPUX)
Next
From: "David E. Wheeler"
Date:
Subject: Re: Domains versus polymorphic functions, redux