Re: seawasp failing, maybe in glibc allocator
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-05-12T18:30:56Z
Lists: pgsql-hackers
> Possibly I have just added "ulimit -c unlimited" in the script, we should see
> the effect on next round.
for def5b065 it ended on on the contrib ltree test:
2021-05-12 20:12:52.528 CEST [3042602:410] pg_regress/ltree LOG: disconnection: session time: 0:00:13.426 user=buildfarm database=contrib_regression_ltree host=[local]
/home/fabien/pg/build-farm-12/buildroot/HEAD/pgsql.build/contrib/ltree/results/ltree.out
2021-05-12 20:12:52.523330311 +0200
@@ -7931,11 +7931,8 @@
(1 row)
SELECT count(*) FROM _ltreetest WHERE t ~ '1.1.1.*' ;
- count
--------
- 19
-(1 row)
-
+ERROR: stack depth limit exceeded
+HINT: Increase the configuration parameter "max_stack_depth" (currently 2048kB), after ensuring the platform's stack depth limit is adequate.
SELECT count(*) FROM _ltreetest WHERE t ~ '*.1' ;
count
-------
Not a core dump, though.
--
Fabien.
Commits
-
Prepare for forthcoming LLVM 13 API change.
- 6ada4fd06666 11.13 landed
- 47d22649e6a2 12.8 landed
- d9c05a9ec493 13.4 landed
- 9b4e4cfe66ff 14.0 landed