From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Remove portability hazard in unsafe_tests/sql/guc_privs.sql. |
Date: | 2022-05-20 17:42:29 |
Message-ID: | E1ns6dx-000JRd-7j@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Remove portability hazard in unsafe_tests/sql/guc_privs.sql.
This new-in-v15 test case assumed it could set max_stack_depth as high
as 2MB. You might think that'd be true on any modern platform but
you'd be wrong, as I found out while experimenting with NetBSD/hppa.
This test is about privileges not platform capabilities, so there seems
no need to use any value greater than the 100kB setting already used
in a couple of places in the core regression tests. There's certainly
no call to expect people to raise their platform's default ulimit just
to run this test.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/5e5fa323350060360799004f96840bbf3cb51e49
Modified Files
--------------
src/test/modules/unsafe_tests/expected/guc_privs.out | 4 ++--
src/test/modules/unsafe_tests/sql/guc_privs.sql | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-05-21 03:02:43 | pgsql: Improve and fix some issues in the TAP tests of pg_upgrade |
Previous Message | Alvaro Herrera | 2022-05-20 17:07:27 | pgsql: Fix mis-merge of result file |