Fork
On 2020/02/18 23:25, torikoshia wrote:
> Fujii-san,
>
> Thanks for your push!
>
> I've run regression tests on the HEAD and REL_1.2 branch and they have finished successfully.
>
> However, when I ran tests on REL_1.1 it
> failed because of the difference of 'pg_bigm.last_update'.
>
> --------------------------
> diff -U3 /home/tori/pg_bigm/expected/pg_bigm.out /home/tori/pg_bigm/results/pg_bigm.out
> --- /home/tori/pg_bigm/expected/pg_bigm.out 2020-02-18 23:11:57.606388619 +0900
> +++ /home/tori/pg_bigm/results/pg_bigm.out 2020-02-18 23:12:02.486400351 +0900
> @@ -10,7 +10,7 @@
> SHOW pg_bigm.last_update;
> pg_bigm.last_update
> ---------------------
> - 2016.10.11
> + 2019.10.03
> ---------------------------
>
> I think this difference has left since 2016.10.11, we don't need to care about
> this, do we?
Thanks for reporting this!
But I could not reproduce this issue. I compiled REL1_1_STABLE branch
of pg_bigm, with PostgreSQL 11, ran the regression test and found the
test finished successfully. Maybe I'm missing something. But could
you confirm that the issue still occurs in your env, and provide
the detail information about how to compile and run the test in
your test?
BTW, "git grep BIGM_LAST_UPDATE" on REL1_1_STABLE branch reported
the followings, in my env.
bigm_op.c:#define BIGM_LAST_UPDATE "2016.10.11"
bigm_op.c: BIGM_LAST_UPDATE,
Regards,
--
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters