auth_constraint.source: fix atmsort

atmsort sometimes treats the triple-dash as the beginning of a table,
which screws up sorting. Use double-dashes to assist with debugging
failures.

src/test/regress/input/auth_constraint.source

---- By design, every boolean query (which doesn't error out) in this test must return true.
---- For reference, 2011-08-30 was a Tuesday!
----
+-- By design, every boolean query (which doesn't error out) in this test must return true.
+-- For reference, 2011-08-30 was a Tuesday!
+--
 CREATE FUNCTION check_auth_time_constraints(cstring, timestamptz)
     RETURNS bool
     AS '@abs_builddir@/regress@DLSUFFIX@'
     LANGUAGE C IMMUTABLE STRICT NO SQL;
 
----
---- invalid timestamp should error out
----
+--
+-- invalid timestamp should error out
+--
 SELECT check_auth_time_constraints('abc', '5');
 
----
---- basic day level constraints
----
+--
+-- basic day level constraints
+--
 CREATE ROLE abc DENY DAY 2;
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 SELECT check_auth_time_constraints('abc', '2011-08-29 23:59:59');
@@ -23,9 +23,9 @@ SELECT NOT check_auth_time_constraints('abc', '2011-08-30 23:59:59');
 SELECT check_auth_time_constraints('abc', '2011-08-31 00:00:00');
 DROP ROLE abc;
 
----
---- basic time level constraints
---- 
+--
+-- basic time level constraints
+--
 CREATE ROLE abc WITH LOGIN DENY DAY 'Saturday';
 DROP ROLE abc;
 CREATE ROLE abc DENY DAY 2 TIME '13:15:34';
@@ -35,9 +35,9 @@ SELECT NOT check_auth_time_constraints('abc', '2011-08-30 13:15:34');
 SELECT check_auth_time_constraints('abc', '2011-08-30 13:15:35');
 DROP ROLE abc;
 
----
---- some similar CREATE ROLE coverage
----
+--
+-- some similar CREATE ROLE coverage
+--
 CREATE ROLE abc DENY BETWEEN DAY 2 AND DAY 3;
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 SELECT check_auth_time_constraints('abc', '2011-08-29 23:59:59');
@@ -70,9 +70,9 @@ SELECT NOT check_auth_time_constraints('abc', '2011-08-31 11:34:53');
 SELECT check_auth_time_constraints('abc', '2011-08-31 11:34:54');
 DROP ROLE abc;
 
----
---- ALTER ROLE grammar coverage (some repetition here)
----
+--
+-- ALTER ROLE grammar coverage (some repetition here)
+--
 CREATE ROLE abc;
 ALTER ROLE abc DENY DAY 2;
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -127,9 +127,9 @@ SELECT NOT check_auth_time_constraints('abc', '2011-08-31 11:34:53');
 SELECT check_auth_time_constraints('abc', '2011-08-31 11:34:54');
 DROP ROLE abc;
 
----
---- very minimal coverage of CREATE USER and ALTER USER
----
+--
+-- very minimal coverage of CREATE USER and ALTER USER
+--
 CREATE USER abc DENY DAY 2;
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 select NOT check_auth_time_constraints('abc', '2011-08-30 12:00:00');
@@ -139,9 +139,9 @@ select NOT check_auth_time_constraints('abc', '2011-08-31 12:00:00');
 ALTER USER abc DROP DENY FOR DAY 2 TIME '12:00:00';
 DROP USER abc;
 
----
---- CREATE ROLE w/ multiple deny specifications
----
+--
+-- CREATE ROLE w/ multiple deny specifications
+--
 CREATE ROLE abc DENY DAY 0 DENY DAY 2 DENY BETWEEN DAY 4 AND DAY 5 TIME '13:00:00';
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 SELECT check_auth_time_constraints('abc', '2011-08-27 23:59:59');
@@ -158,9 +158,9 @@ SELECT NOT check_auth_time_constraints('abc', '2011-09-02 13:00:00');
 SELECT check_auth_time_constraints('abc', '2011-09-02 13:00:01');
 DROP ROLE abc;
 
----
---- ALTER ROLE w/ multiple deny specifications
----
+--
+-- ALTER ROLE w/ multiple deny specifications
+--
 CREATE ROLE abc;
 ALTER ROLE abc DENY DAY 0 DENY DAY 2 DENY BETWEEN DAY 4 AND DAY 5 TIME '13:00:00';
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -178,10 +178,10 @@ SELECT NOT check_auth_time_constraints('abc', '2011-09-02 13:00:00');
 SELECT check_auth_time_constraints('abc', '2011-09-02 13:00:01');
 DROP ROLE abc;
 
----
---- ALTER ROLE DROP
---- This syntax drops any rule that *overlaps* with the specified point/interval.
----
+--
+-- ALTER ROLE DROP
+-- This syntax drops any rule that *overlaps* with the specified point/interval.
+--
 CREATE ROLE abc DENY DAY 2;
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 SELECT NOT check_auth_time_constraints('abc', '2011-08-30 12:00:00');
@@ -207,33 +207,33 @@ ALTER ROLE abc DENY DAY 0 DENY DAY 1;
 ALTER ROLE abc DROP DENY FOR DAY 2;
 DROP ROLE abc;
 
----
---- ALTER ROLE w/ multiple deny and drop specifications
---- This should error out, as the expected behavior isn't quite intuitive.
----
+--
+-- ALTER ROLE w/ multiple deny and drop specifications
+-- This should error out, as the expected behavior isn't quite intuitive.
+--
 CREATE ROLE abc;
 ALTER ROLE abc DENY DAY 0 DENY DAY 1 DENY DAY 2 DROP DENY FOR DAY 1;
 DROP ROLE abc;
 
----
---- DROP ROLE must release associated auth. constraints
----
+--
+-- DROP ROLE must release associated auth. constraints
+--
 CREATE ROLE abc DENY DAY 0 DENY DAY 1 DENY DAY 3 TIME '3:00 PM';
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 DROP ROLE abc;
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 
----
---- Wrap-around intervals
----
+--
+-- Wrap-around intervals
+--
 CREATE ROLE abc DENY BETWEEN DAY 6 TIME '12:00:00' AND DAY 0;
 CREATE ROLE abc;
 ALTER ROLE abc DENY BETWEEN DAY 5 AND DAY 1;
 DROP ROLE abc;
 
----
---- English days of week
----
+--
+-- English days of week
+--
 CREATE ROLE abc DENY BETWEEN DAY 'Tuesday' TIME '12:00:00' AND DAY 2 TIME '1:00 PM';
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 SELECT check_auth_time_constraints('abc', '2011-08-30 11:59:59');
@@ -242,21 +242,21 @@ SELECT NOT check_auth_time_constraints('abc', '2011-08-30 13:00:00');
 SELECT check_auth_time_constraints('abc', '2011-08-30 13:00:01');
 DROP ROLE abc;
 
----
---- English days of week (negative)
----
+--
+-- English days of week (negative)
+--
 CREATE ROLE abc DENY DAY 'Monkey' TIME '12:00:00';
 CREATE ROLE abc WITH LOGIN DENY BETWEEN DAY 'Monday' TIME '00:00' AND DAY 'Monday' TIME '25:00';
 CREATE ROLE abc WITH LOGIN DENY BETWEEN DAY 'Monday' TIME '01:65 AM' AND DAY 'Monday' TIME '12:00 PM';
 CREATE ROLE abc WITH LOGIN DENY BETWEEN DAY 'Monday' TIME '-01:00' AND DAY 'Monday' TIME '06:00 PM';
 CREATE ROLE abc DENY BETWEEN DAY 'Monday' TIME '00:00' AND DAY 'Monday' TIME '25:00';
 
----
---- What is '24:00:00'? Apparently, '2011-08-30 24:00:00' == '2011-08-31 00:00:00'.
---- But interpreted as a sole time value, '24:00:00' != '00:00:00' and
---- '24:00:00' > '23:59:59'. So, the following three queries should evaluate to true.
---- In other words, there is no way for the current time to ever be '24:00:00'.
----
+--
+-- What is '24:00:00'? Apparently, '2011-08-30 24:00:00' == '2011-08-31 00:00:00'.
+-- But interpreted as a sole time value, '24:00:00' != '00:00:00' and
+-- '24:00:00' > '23:59:59'. So, the following three queries should evaluate to true.
+-- In other words, there is no way for the current time to ever be '24:00:00'.
+--
 CREATE ROLE abc DENY DAY 2 TIME '24:00:00';
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
 SELECT check_auth_time_constraints('abc', '2011-08-30 23:59:59');
@@ -265,9 +265,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 00:00:00');
 DROP ROLE abc;
 
 
----
---- Inheritance of time constraints (negative)
----
+--
+-- Inheritance of time constraints (negative)
+--
 CREATE ROLE abc DENY BETWEEN DAY 0 AND DAY 6;
 SELECT NOT check_auth_time_constraints('abc', '2011-08-31 12:00:00');
 CREATE ROLE foo IN ROLE abc;
@@ -275,9 +275,9 @@ SELECT check_auth_time_constraints('foo', '2011-08-31 12:00:00');
 DROP ROLE foo;
 DROP ROLE abc;
 
----
---- Exercise catalog DML and pg_auth_time_constraint trigger
----
+--
+-- Exercise catalog DML and pg_auth_time_constraint trigger
+--
 SET allow_system_table_mods = dml;
 CREATE ROLE abc;
 insert into pg_auth_time_constraint (select oid, 2, '12:00:00', 3, '12:00:00' from pg_authid where rolname = 'abc');
@@ -300,9 +300,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 00:00:00');
 DROP ROLE abc;
 RESET allow_system_table_mods;
 
----
---- Superuser testing across CREATE ROLE, ALTER ROLE, and trigger
----
+--
+-- Superuser testing across CREATE ROLE, ALTER ROLE, and trigger
+--
 
 create role abc with login nosuperuser nocreaterole;
 drop role abc;

src/test/regress/output/auth_constraint.source

---- By design, every boolean query (which doesn't error out) in this test must return true.
---- For reference, 2011-08-30 was a Tuesday!
----
+-- By design, every boolean query (which doesn't error out) in this test must return true.
+-- For reference, 2011-08-30 was a Tuesday!
+--
 CREATE FUNCTION check_auth_time_constraints(cstring, timestamptz)
     RETURNS bool
     AS '@abs_builddir@/regress@DLSUFFIX@'
     LANGUAGE C IMMUTABLE STRICT NO SQL;
----
---- invalid timestamp should error out
----
+--
+-- invalid timestamp should error out
+--
 SELECT check_auth_time_constraints('abc', '5');
 ERROR:  invalid input syntax for type timestamp with time zone: "5"
 LINE 1: SELECT check_auth_time_constraints('abc', '5');
                                                   ^
----
---- basic day level constraints
----
+--
+-- basic day level constraints
+--
 CREATE ROLE abc DENY DAY 2;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -54,9 +54,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 00:00:00');
 (1 row)
 
 DROP ROLE abc;
----
---- basic time level constraints
---- 
+--
+-- basic time level constraints
+--
 CREATE ROLE abc WITH LOGIN DENY DAY 'Saturday';
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 DROP ROLE abc;
@@ -87,9 +87,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-30 13:15:35');
 (1 row)
 
 DROP ROLE abc;
----
---- some similar CREATE ROLE coverage
----
+--
+-- some similar CREATE ROLE coverage
+--
 CREATE ROLE abc DENY BETWEEN DAY 2 AND DAY 3;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -222,9 +222,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 11:34:54');
 (1 row)
 
 DROP ROLE abc;
----
---- ALTER ROLE grammar coverage (some repetition here)
----
+--
+-- ALTER ROLE grammar coverage (some repetition here)
+--
 CREATE ROLE abc;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 ALTER ROLE abc DENY DAY 2;
@@ -429,9 +429,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 11:34:54');
 (1 row)
 
 DROP ROLE abc;
----
---- very minimal coverage of CREATE USER and ALTER USER
----
+--
+-- very minimal coverage of CREATE USER and ALTER USER
+--
 CREATE USER abc DENY DAY 2;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -463,9 +463,9 @@ select NOT check_auth_time_constraints('abc', '2011-08-31 12:00:00');
 ALTER USER abc DROP DENY FOR DAY 2 TIME '12:00:00';
 NOTICE:  dropping DENY rule for "abc" between Tuesday 00:00:00 and Tuesday 24:00:00
 DROP USER abc;
----
---- CREATE ROLE w/ multiple deny specifications
----
+--
+-- CREATE ROLE w/ multiple deny specifications
+--
 CREATE ROLE abc DENY DAY 0 DENY DAY 2 DENY BETWEEN DAY 4 AND DAY 5 TIME '13:00:00';
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -549,9 +549,9 @@ SELECT check_auth_time_constraints('abc', '2011-09-02 13:00:01');
 (1 row)
 
 DROP ROLE abc;
----
---- ALTER ROLE w/ multiple deny specifications
----
+--
+-- ALTER ROLE w/ multiple deny specifications
+--
 CREATE ROLE abc;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 ALTER ROLE abc DENY DAY 0 DENY DAY 2 DENY BETWEEN DAY 4 AND DAY 5 TIME '13:00:00';
@@ -636,10 +636,10 @@ SELECT check_auth_time_constraints('abc', '2011-09-02 13:00:01');
 (1 row)
 
 DROP ROLE abc;
----
---- ALTER ROLE DROP
---- This syntax drops any rule that *overlaps* with the specified point/interval.
----
+--
+-- ALTER ROLE DROP
+-- This syntax drops any rule that *overlaps* with the specified point/interval.
+--
 CREATE ROLE abc DENY DAY 2;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -718,19 +718,19 @@ ALTER ROLE abc DENY DAY 0 DENY DAY 1;
 ALTER ROLE abc DROP DENY FOR DAY 2;
 ERROR:  cannot find matching DENY rules for "abc"
 DROP ROLE abc;
----
---- ALTER ROLE w/ multiple deny and drop specifications
---- This should error out, as the expected behavior isn't quite intuitive.
----
+--
+-- ALTER ROLE w/ multiple deny and drop specifications
+-- This should error out, as the expected behavior isn't quite intuitive.
+--
 CREATE ROLE abc;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 ALTER ROLE abc DENY DAY 0 DENY DAY 1 DENY DAY 2 DROP DENY FOR DAY 1;
 ERROR:  conflicting or redundant options
 HINT:  DENY and DROP DENY cannot be used in the same ALTER ROLE statement.
 DROP ROLE abc;
----
---- DROP ROLE must release associated auth. constraints
----
+--
+-- DROP ROLE must release associated auth. constraints
+--
 CREATE ROLE abc DENY DAY 0 DENY DAY 1 DENY DAY 3 TIME '3:00 PM';
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -747,9 +747,9 @@ select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_aut
 -----------+------------+---------+----------
 (0 rows)
 
----
---- Wrap-around intervals
----
+--
+-- Wrap-around intervals
+--
 CREATE ROLE abc DENY BETWEEN DAY 6 TIME '12:00:00' AND DAY 0;
 ERROR:  time interval must not wrap around
 CREATE ROLE abc;
@@ -757,9 +757,9 @@ NOTICE:  resource queue required -- using default resource queue "pg_default"
 ALTER ROLE abc DENY BETWEEN DAY 5 AND DAY 1;
 ERROR:  time interval must not wrap around
 DROP ROLE abc;
----
---- English days of week
----
+--
+-- English days of week
+--
 CREATE ROLE abc DENY BETWEEN DAY 'Tuesday' TIME '12:00:00' AND DAY 2 TIME '1:00 PM';
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -793,9 +793,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-30 13:00:01');
 (1 row)
 
 DROP ROLE abc;
----
---- English days of week (negative)
----
+--
+-- English days of week (negative)
+--
 CREATE ROLE abc DENY DAY 'Monkey' TIME '12:00:00';
 ERROR:  invalid weekday name "Monkey"
 HINT:  Day of week must be one of 'Sunday', 'Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday'.
@@ -807,12 +807,12 @@ CREATE ROLE abc WITH LOGIN DENY BETWEEN DAY 'Monday' TIME '-01:00' AND DAY 'Mond
 ERROR:  invalid input syntax for type time: "-01:00"
 CREATE ROLE abc DENY BETWEEN DAY 'Monday' TIME '00:00' AND DAY 'Monday' TIME '25:00';
 ERROR:  date/time field value out of range: "25:00"
----
---- What is '24:00:00'? Apparently, '2011-08-30 24:00:00' == '2011-08-31 00:00:00'.
---- But interpreted as a sole time value, '24:00:00' != '00:00:00' and
---- '24:00:00' > '23:59:59'. So, the following three queries should evaluate to true.
---- In other words, there is no way for the current time to ever be '24:00:00'.
----
+--
+-- What is '24:00:00'? Apparently, '2011-08-30 24:00:00' == '2011-08-31 00:00:00'.
+-- But interpreted as a sole time value, '24:00:00' != '00:00:00' and
+-- '24:00:00' > '23:59:59'. So, the following three queries should evaluate to true.
+-- In other words, there is no way for the current time to ever be '24:00:00'.
+--
 CREATE ROLE abc DENY DAY 2 TIME '24:00:00';
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 select c.start_day, c.start_time, c.end_day, c.end_time from pg_authid a, pg_auth_time_constraint c where c.authid = a.oid and a.rolname = 'abc';
@@ -840,9 +840,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 00:00:00');
 (1 row)
 
 DROP ROLE abc;
----
---- Inheritance of time constraints (negative)
----
+--
+-- Inheritance of time constraints (negative)
+--
 CREATE ROLE abc DENY BETWEEN DAY 0 AND DAY 6;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 SELECT NOT check_auth_time_constraints('abc', '2011-08-31 12:00:00');
@@ -861,9 +861,9 @@ SELECT check_auth_time_constraints('foo', '2011-08-31 12:00:00');
 
 DROP ROLE foo;
 DROP ROLE abc;
----
---- Exercise catalog DML and pg_auth_time_constraint trigger
----
+--
+-- Exercise catalog DML and pg_auth_time_constraint trigger
+--
 SET allow_system_table_mods = dml;
 CREATE ROLE abc;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
@@ -943,9 +943,9 @@ SELECT check_auth_time_constraints('abc', '2011-08-31 00:00:00');
 
 DROP ROLE abc;
 RESET allow_system_table_mods;
----
---- Superuser testing across CREATE ROLE, ALTER ROLE, and trigger
----
+--
+-- Superuser testing across CREATE ROLE, ALTER ROLE, and trigger
+--
 create role abc with login nosuperuser nocreaterole;
 NOTICE:  resource queue required -- using default resource queue "pg_default"
 drop role abc;