Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Christoph, what beta2 change was it that fixed that problem? I'm having exactly the same regression test failure in version 10.1 (not beta) running on Solaris 9 Compiler used: GCC 4.6.4 CFLAGS: -O2 -m64 On 13/07/2017 20:05, Christoph Berg wrote: Re: To Andres Freund 2017-05-24 <20170524170921.7pykzbt54dlfk...@msg.df7cb.de> If we had a typo or something in that code, the build farm should have caught it by now. I would try compiling with lower -O and see what happens. Trying -O0 now. Sorry for the late reply, I was hoping to catch you on IRC, but then didn't manage to be around at a time that would fit the timezone shift. The -O0 build passed the regression tests. Not sure what that means for our problem, though. Fwiw, the problem is fixed with beta2, even with -O2: https://buildd.debian.org/status/logs.php?pkg=postgresql-10=sparc64 Christoph -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Re: To Andres Freund 2017-05-24 <20170524170921.7pykzbt54dlfk...@msg.df7cb.de> > > > If we had a typo or something in that code, the build farm should have > > > caught it by now. > > > > > > I would try compiling with lower -O and see what happens. > > > > Trying -O0 now. > > Sorry for the late reply, I was hoping to catch you on IRC, but then > didn't manage to be around at a time that would fit the timezone > shift. > > The -O0 build passed the regression tests. Not sure what that means > for our problem, though. Fwiw, the problem is fixed with beta2, even with -O2: https://buildd.debian.org/status/logs.php?pkg=postgresql-10=sparc64 Christoph -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Re: To Andres Freund 2017-05-18 <20170518192924.jkrzevlencp3g...@msg.df7cb.de> > > If we had a typo or something in that code, the build farm should have > > caught it by now. > > > > I would try compiling with lower -O and see what happens. > > Trying -O0 now. Sorry for the late reply, I was hoping to catch you on IRC, but then didn't manage to be around at a time that would fit the timezone shift. The -O0 build passed the regression tests. Not sure what that means for our problem, though. > Re: Andres Freund 2017-05-18 > <20170518184811.7c44jcvwjvnzc...@alap3.anarazel.de> > > Weird. Christoph, IIRC you can help gaining access to a porter machine > > to reproduce this? > > I'll let the build run over night (the machine has 32 cores but is > dead slow) and see what I can arrange tomorrow. (Peter will already > have access, it's notker.debian.net.) Will send you a separate mail for that. Christoph -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Re: Peter Eisentraut 2017-05-18 <7a4d3b0f-78da-2a5b-7f3b-8b3509c1e...@2ndquadrant.com> > If we had a typo or something in that code, the build farm should have > caught it by now. > > I would try compiling with lower -O and see what happens. Trying -O0 now. Re: Andres Freund 2017-05-18 <20170518184811.7c44jcvwjvnzc...@alap3.anarazel.de> > Weird. Christoph, IIRC you can help gaining access to a porter machine > to reproduce this? I'll let the build run over night (the machine has 32 cores but is dead slow) and see what I can arrange tomorrow. (Peter will already have access, it's notker.debian.net.) Christoph -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
On 5/18/17 10:11, Tom Lane wrote: > Well, that's just wacko. Somehow sequence.c's init_params() must > be falling down on the job in selecting the right seqform->seqmin, > but I'm darned if I see anything that's either wrong or potentially > machine-dependent in that code. It almost looks like it must be > a compiler bug, though I hesitate to jump to that conclusion so > quickly. Peter, any ideas? If we had a typo or something in that code, the build farm should have caught it by now. I would try compiling with lower -O and see what happens. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
On 2017-05-18 10:11:48 -0400, Tom Lane wrote: > Christoph Bergwrites: > > *** 34,44 > > --- 34,47 > > CREATE SEQUENCE sequence_test7 AS bigint; > > CREATE SEQUENCE sequence_test8 AS integer MAXVALUE 10; > > CREATE SEQUENCE sequence_test9 AS integer INCREMENT BY -1; > > + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data > > type integer > > CREATE SEQUENCE sequence_test10 AS integer MINVALUE -10 START 1; > > CREATE SEQUENCE sequence_test11 AS smallint; > > CREATE SEQUENCE sequence_test12 AS smallint INCREMENT -1; > > + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data > > type smallint > > CREATE SEQUENCE sequence_test13 AS smallint MINVALUE -32768; > > CREATE SEQUENCE sequence_test14 AS smallint MAXVALUE 32767 INCREMENT -1; > > + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data > > type smallint > > CREATE SEQUENCE sequence_testx AS text; > > ERROR: sequence type must be smallint, integer, or bigint > > CREATE SEQUENCE sequence_testx AS nosuchtype; > > Well, that's just wacko. Somehow sequence.c's init_params() must > be falling down on the job in selecting the right seqform->seqmin, > but I'm darned if I see anything that's either wrong or potentially > machine-dependent in that code. It almost looks like it must be > a compiler bug, though I hesitate to jump to that conclusion so > quickly. Peter, any ideas? Weird. Christoph, IIRC you can help gaining access to a porter machine to reproduce this? - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Christoph Bergwrites: > *** 34,44 > --- 34,47 > CREATE SEQUENCE sequence_test7 AS bigint; > CREATE SEQUENCE sequence_test8 AS integer MAXVALUE 10; > CREATE SEQUENCE sequence_test9 AS integer INCREMENT BY -1; > + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data > type integer > CREATE SEQUENCE sequence_test10 AS integer MINVALUE -10 START 1; > CREATE SEQUENCE sequence_test11 AS smallint; > CREATE SEQUENCE sequence_test12 AS smallint INCREMENT -1; > + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data > type smallint > CREATE SEQUENCE sequence_test13 AS smallint MINVALUE -32768; > CREATE SEQUENCE sequence_test14 AS smallint MAXVALUE 32767 INCREMENT -1; > + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data > type smallint > CREATE SEQUENCE sequence_testx AS text; > ERROR: sequence type must be smallint, integer, or bigint > CREATE SEQUENCE sequence_testx AS nosuchtype; Well, that's just wacko. Somehow sequence.c's init_params() must be falling down on the job in selecting the right seqform->seqmin, but I'm darned if I see anything that's either wrong or potentially machine-dependent in that code. It almost looks like it must be a compiler bug, though I hesitate to jump to that conclusion so quickly. Peter, any ideas? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Re: Tom Lane 2017-05-17 <30016.1495041...@sss.pgh.pa.us> > Christoph Bergwrites: > > The sequence regression tests are failing on Debian/sparc64: > > ... > > (This is only the last 100 lines of regression.diffs, if it helps I > > can try rebuilding and grabbing the full file.) > > Yes please. What we can see here looks to be just fallout from > a failure earlier in the run. *** /home/myon/postgresql-10-10~beta1/build/../src/test/regress/expected/sequence.out 2017-05-15 23:20:59.0 +0200 --- /home/myon/postgresql-10-10~beta1/build/src/test/regress/results/sequence.out 2017-05-17 22:27:28.834225769 +0200 *** *** 34,44 --- 34,47 CREATE SEQUENCE sequence_test7 AS bigint; CREATE SEQUENCE sequence_test8 AS integer MAXVALUE 10; CREATE SEQUENCE sequence_test9 AS integer INCREMENT BY -1; + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data type integer CREATE SEQUENCE sequence_test10 AS integer MINVALUE -10 START 1; CREATE SEQUENCE sequence_test11 AS smallint; CREATE SEQUENCE sequence_test12 AS smallint INCREMENT -1; + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data type smallint CREATE SEQUENCE sequence_test13 AS smallint MINVALUE -32768; CREATE SEQUENCE sequence_test14 AS smallint MAXVALUE 32767 INCREMENT -1; + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data type smallint CREATE SEQUENCE sequence_testx AS text; ERROR: sequence type must be smallint, integer, or bigint CREATE SEQUENCE sequence_testx AS nosuchtype; *** *** 54,66 --- 57,73 ERROR: MAXVALUE (10) is out of range for sequence data type smallint ALTER SEQUENCE sequence_test8 AS smallint MAXVALUE 2; -- ok now ALTER SEQUENCE sequence_test9 AS smallint; -- success, min will be adjusted + ERROR: relation "sequence_test9" does not exist ALTER SEQUENCE sequence_test10 AS smallint; -- fail, min has to be adjusted ERROR: MINVALUE (-10) is out of range for sequence data type smallint ALTER SEQUENCE sequence_test10 AS smallint MINVALUE -2; -- ok now ALTER SEQUENCE sequence_test11 AS int; -- max will be adjusted ALTER SEQUENCE sequence_test12 AS int; -- min will be adjusted + ERROR: relation "sequence_test12" does not exist ALTER SEQUENCE sequence_test13 AS int; -- min and max will be adjusted + ERROR: MINVALUE (-9223372036854775808) is out of range for sequence data type integer ALTER SEQUENCE sequence_test14 AS int; -- min and max will be adjusted + ERROR: relation "sequence_test14" does not exist --- --- test creation of SERIAL column --- *** *** 477,485 --+-++---+---+-+---+-+--+-+---+-- regression | public | sequence_test10| smallint | 16 | 2 | 0 | 1 | -2 | 32767 | 1 | NO regression | public | sequence_test11| integer | 32 | 2 | 0 | 1 | 1 | 2147483647 | 1 | NO ! regression | public | sequence_test12| integer | 32 | 2 | 0 | -1 | -2147483648 | -1 | -1| NO ! regression | public | sequence_test13| integer | 32 | 2 | 0 | -32768 | -2147483648 | 2147483647 | 1 | NO ! regression | public | sequence_test14| integer | 32 | 2 | 0 | 32767 | -2147483648 | 2147483647 | -1| NO regression | public | sequence_test2 | bigint| 64 | 2 | 0 | 32 | 5 | 36 | 4 | YES regression | public | sequence_test3 | bigint| 64 | 2 | 0 | 1 | 1 | 9223372036854775807 | 1 | NO regression | public | sequence_test4 | bigint| 64 | 2 | 0 | -1 | -9223372036854775808 | -1 | -1| NO --- 484,490 --+-++---+---+-+---+-+--+-+---+-- regression | public | sequence_test10| smallint | 16 | 2 | 0 | 1
Re: [HACKERS] 10beta1 sequence regression failure on sparc64
Christoph Bergwrites: > The sequence regression tests are failing on Debian/sparc64: > ... > (This is only the last 100 lines of regression.diffs, if it helps I > can try rebuilding and grabbing the full file.) Yes please. What we can see here looks to be just fallout from a failure earlier in the run. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] 10beta1 sequence regression failure on sparc64
The sequence regression tests are failing on Debian/sparc64: sequence ... FAILED polymorphism ... ok rowtypes ... ok returning... ok largeobject ... ok with ... ok xml ... ok test identity ... ok test event_trigger... ok test stats... ok == shutting down postmaster == 1 of 178 tests failed. The differences that caused some tests to fail can be viewed in the file "/<>/build/src/test/regress/regression.diffs". A copy of the test summary that you see above is saved in the file "/<>/build/src/test/regress/regression.out". GNUmakefile:130: recipe for target 'check' failed make[2]: *** [check] Error 1 make[2]: Leaving directory '/<>/build/src/test/regress' Makefile:28: recipe for target 'check-regress-recurse' failed make[1]: *** [check-regress-recurse] Error 2 make[1]: Leaving directory '/<>/build/src/test' GNUmakefile:69: recipe for target 'check-world-src/test-recurse' failed make: *** [check-world-src/test-recurse] Error 2 make: Leaving directory '/<>/build' build/src/test/regress/regression.diffs *** 477,485 --+-++---+---+-+---+-+--+-+---+-- regression | public | sequence_test10| smallint | 16 | 2 | 0 | 1 | -2 | 32767 | 1 | NO regression | public | sequence_test11| integer | 32 | 2 | 0 | 1 | 1 | 2147483647 | 1 | NO ! regression | public | sequence_test12| integer | 32 | 2 | 0 | -1 | -2147483648 | -1 | -1| NO ! regression | public | sequence_test13| integer | 32 | 2 | 0 | -32768 | -2147483648 | 2147483647 | 1 | NO ! regression | public | sequence_test14| integer | 32 | 2 | 0 | 32767 | -2147483648 | 2147483647 | -1| NO regression | public | sequence_test2 | bigint| 64 | 2 | 0 | 32 | 5 | 36 | 4 | YES regression | public | sequence_test3 | bigint| 64 | 2 | 0 | 1 | 1 | 9223372036854775807 | 1 | NO regression | public | sequence_test4 | bigint| 64 | 2 | 0 | -1 | -9223372036854775808 | -1 | -1| NO --- 484,490 --+-++---+---+-+---+-+--+-+---+-- regression | public | sequence_test10| smallint | 16 | 2 | 0 | 1 | -2 | 32767 | 1 | NO regression | public | sequence_test11| integer | 32 | 2 | 0 | 1 | 1 | 2147483647 | 1 | NO ! regression | public | sequence_test13| smallint | 16 | 2 | 0 | -32768 | -32768 | 32767 | 1 | NO regression | public | sequence_test2 | bigint| 64 | 2 | 0 | 32 | 5 | 36 | 4 | YES regression | public | sequence_test3 | bigint| 64 | 2 | 0 | 1 | 1 | 9223372036854775807 | 1 | NO regression | public | sequence_test4 | bigint| 64 | 2 | 0 | -1 | -9223372036854775808 | -1 | -1| NO *** *** 487,500 regression | public | sequence_test6 | smallint | 16 | 2 | 0 | 1 | 1 | 32767 | 1 | NO