From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Steve Singer <steve(at)ssinger(dot)info> |
Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: changeset generation v5-01 - Patches & git tree |
Date: | 2013-07-05 13:34:32 |
Message-ID: | 20130705133432.GC11640@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2013-07-05 09:28:45 -0400, Steve Singer wrote:
> On 07/05/2013 08:03 AM, Andres Freund wrote:
> >On 2013-06-27 21:52:03 -0700, Kevin Grittner wrote:
> >>Tried that, too, and problem persists. The log shows the last commit on
> >>your branch as 022c2da1873de2fbc93ae524819932719ca41bdb.
> >Ok. I think I have a slight idea what's going on. Could you check
> >whether recompiling with -O0 "fixes" the issue?
> >
> >There's something strange going on here, not sure whether it's just a
> >bug that's hidden, by either not doing optimizations or by adding more
> >elog()s, or wheter it's a compiler bug.
>
> I am getting the same test failure Kevin is seeing.
> This is on a x64 Debian wheezy machine with
> gcc (Debian 4.7.2-5) 4.7.2
>
> Building with -O0 results in passing tests.
Does the patch from
http://archives.postgresql.org/message-id/20130705132513.GB11640%40awork2.anarazel.de
or the git tree (which is rebased ontop of the mvcc catalog commit from
robert which needs some changes) fix it, even with optimizations?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-07-05 13:39:09 | Re: strange IS NULL behaviour |
Previous Message | Steve Singer | 2013-07-05 13:28:45 | Re: changeset generation v5-01 - Patches & git tree |