Re: Alignment padding bytes in arrays vs the planner

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

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, May 24, 2011 at 2:11 PM, Noah Misch <noah(at)leadboat(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-05-24 18:21:02 Re: Alignment padding bytes in arrays vs the planner
Previous Message David E. Wheeler 2011-05-24 18:17:59 Re: Domains versus polymorphic functions, redux