Re: Another bug(?) turned up by the llvm optimization checker

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Another bug(?) turned up by the llvm optimization checker
Date: 2013-11-11 15:31:25
Message-ID: CAM-w4HNrp13ya2EDg1fOk3HV9gVgt3QZKwg0dkof83V82h+hyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 11, 2013 at 4:00 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> In any case, the issue looks bigger than just addRangeTableEntry
> itself. Do you want to write up a patch?
>

I was going to include it in the overflow patch but I'm now thinking I
should make it a separate commit to make sure the change in the contract
isn't buried in overflow check changes that are supposed to not change
functionality. I'll do that.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2013-11-11 15:43:05 Re: TABLE not synonymous with SELECT * FROM?
Previous Message Tom Lane 2013-11-11 15:26:18 Re: pgsql: Fix whitespace issues found by git diff --check, add gitattribut