commit adaff75cb96ec842d15e15df2ee42dd4b3fa1349 Author: Jacob Champion Date: Tue Aug 16 09:32:45 2022 -0700 squash! SYSTEM_USER implementation Check the contents of SYSTEM_USER in the Kerberos tests, not just its existence. diff --git a/src/test/kerberos/t/001_auth.pl b/src/test/kerberos/t/001_auth.pl index 7ce3b33da6..be0dd7c62d 100644 --- a/src/test/kerberos/t/001_auth.pl +++ b/src/test/kerberos/t/001_auth.pl @@ -178,11 +178,11 @@ $node->safe_psql('postgres', 'CREATE USER test1;'); # Set up a table for SYSTEM_USER parallel worker testing. $node->safe_psql('postgres', - 'CREATE TABLE nulls (n) AS SELECT NULL FROM generate_series(1, 200000);' + "CREATE TABLE ids (id) AS SELECT 'gss:test1\@$realm' FROM generate_series(1, 200000);" ); $node->safe_psql('postgres', - 'GRANT SELECT ON nulls TO public;' + 'GRANT SELECT ON ids TO public;' ); note "running tests"; @@ -333,7 +333,7 @@ test_query( . "SET parallel_setup_cost TO 0;\n" . "SET parallel_tuple_cost TO 0;\n" . "SET max_parallel_workers_per_gather TO 2;\n" - . "SELECT bool_and(SYSTEM_USER IS DISTINCT FROM n) FROM nulls;", + . "SELECT bool_and(SYSTEM_USER = id) FROM ids;", qr/^t$/s, 'gssencmode=require', 'testing system_user with parallel workers');