Re: Another bug(?) turned up by the llvm optimization checker - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Another bug(?) turned up by the llvm optimization checker
Date
Msg-id CAM-w4HNrp13ya2EDg1fOk3HV9gVgt3QZKwg0dkof83V82h+hyQ@mail.gmail.com
Whole thread Raw
In response to Re: Another bug(?) turned up by the llvm optimization checker  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On Mon, Nov 11, 2013 at 4:00 AM, Tom Lane <span
dir="ltr"><<ahref="mailto:tgl@sss.pgh.pa.us" target="_blank">tgl@sss.pgh.pa.us</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3zb"
style="overflow:hidden">In any case, the issue looks bigger than just addRangeTableEntry<br /> itself.  Do you want to
writeup a patch?</div></blockquote></div><br /></div><div class="gmail_extra">I was going to include it in the overflow
patchbut I'm now thinking I should make it a separate commit to make sure the change in the contract isn't buried in
overflowcheck changes that are supposed to not change functionality. I'll do that.<br /></div><div
class="gmail_extra"><brclear="all" /><br />-- <br />greg<br /></div></div> 

pgsql-hackers by date:

Previous
From: Ishaya Bhatt
Date:
Subject: Re: Datatyp of a column
Next
From: David Johnston
Date:
Subject: Re: TABLE not synonymous with SELECT * FROM?