Re: Issue with v11.0 within jsonb_plperl tests in 32bit on AIX - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Issue with v11.0 within jsonb_plperl tests in 32bit on AIX
Date
Msg-id 20181106174501.2bgasgrfbssgx2db@alvherre.pgsql
Whole thread Raw
In response to RE: Issue with v11.0 within jsonb_plperl tests in 32bit on AIX  ("REIX, Tony" <tony.reix@atos.net>)
Responses RE: Issue with v11.0 within jsonb_plperl tests in 32bit on AIX  ("REIX, Tony" <tony.reix@atos.net>)
List pgsql-hackers
On 2018-Nov-06, REIX, Tony wrote:

> Hummm The buildfarm does show that these tests are OK on AIX machines in 32bit, with GCC 4.8.1 .
> 
> Nuts !
> 
> 
> Attached is the full diff between the expected results and the real results.

Standard diffs are awful to read.  Would you mind using context or
unified diffs please (diff -c or diff -u)?  Also, keep in mind that the
regression tests save a file "regression.diffs" with all the diffs in
context format, so there's no need to create them yourself.

That said, this looks like there's an ABI mismatch somewhere, where
this:

<             roundtrip            
< ---------------------------------
<  {"1": {"2": [3, 4, 5]}, "2": 3}

ends up as

{
    "1": {
        "2": [

0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000531017013119972,

0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000531146529464635,

0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000530757980430645
        ]
    },
    "2":
0.0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000026632835514017
}

Note that keys seem okay, but the values are corrupted.  (I wonder if
those values are actually representable in 32 bits.)  What catches my
attention is that the values for "3" in the two places where it appears
are different.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Emre Hasegeli
Date:
Subject: Re: New Defects reported by Coverity Scan for PostgreSQL
Next
From: Tomas Vondra
Date:
Subject: Re: valgrind issues on Fedora 28