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=y_K0BmpvnYgiBkyGMEp0HhhBorA@mail.gmail.com
Whole thread Raw
In response to Re: Alignment padding bytes in arrays vs the planner  (Tom Lane <tgl@sss.pgh.pa.us>)
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:18 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Tue, May 24, 2011 at 2:11 PM, Noah Misch <noah@leadboat.com> wrote:
>>> 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.
>
> Yeah.  I'm in process of doing that, actually.

Excellent.  Are you going to look at MauMau's patch for bug #6011 also?

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Alignment padding bytes in arrays vs the planner
Next
From: Tom Lane
Date:
Subject: Re: Domains versus polymorphic functions, redux