Make get_stack_depth_rlimit() handle RLIM_INFINITY more sanely.
Tom Lane <tgl@sss.pgh.pa.us>
Make get_stack_depth_rlimit() handle RLIM_INFINITY more sanely. Rather than considering this result as meaning "unknown", report LONG_MAX. This won't change what superusers can set max_stack_depth to, but it will cause InitializeGUCOptions() to set the built-in default to 2MB not 100kB. The latter seems like a fairly unreasonable interpretation of "infinity". Per my investigation of odd buildfarm results as well as an old complaint from Heikki. Since this should persuade all the buildfarm animals to use a reasonable stack depth setting during "make check", revert previous patch that dumbed down a recursive regression test to only 5 levels.
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/tcop/postgres.c | modified | +8 −4 |
| src/backend/utils/misc/guc.c | modified | +2 −2 |
| src/test/regress/expected/plpgsql.out | modified | +1 −1 |
| src/test/regress/sql/plpgsql.sql | modified | +1 −1 |