Add ORDER BY to some regression test queries
Apparently, an unrelated patch introduced some variation on the build farm. Reported-by: Magnus Hagander <magnus@hagander.net>
This commit is contained in:
parent
aaf0432572
commit
7e3c54168d
|
@ -474,26 +474,27 @@ CREATE FUNCTION functest_IS_7()
|
||||||
SELECT r0.routine_name, r1.routine_name
|
SELECT r0.routine_name, r1.routine_name
|
||||||
FROM information_schema.routine_routine_usage rru
|
FROM information_schema.routine_routine_usage rru
|
||||||
JOIN information_schema.routines r0 ON r0.specific_name = rru.specific_name
|
JOIN information_schema.routines r0 ON r0.specific_name = rru.specific_name
|
||||||
JOIN information_schema.routines r1 ON r1.specific_name = rru.routine_name;
|
JOIN information_schema.routines r1 ON r1.specific_name = rru.routine_name
|
||||||
|
ORDER BY 1, 2;
|
||||||
routine_name | routine_name
|
routine_name | routine_name
|
||||||
----------------+----------------
|
----------------+----------------
|
||||||
functest_is_4b | functest_is_4a
|
functest_is_4b | functest_is_4a
|
||||||
(1 row)
|
(1 row)
|
||||||
|
|
||||||
SELECT routine_name, sequence_name FROM information_schema.routine_sequence_usage;
|
SELECT routine_name, sequence_name FROM information_schema.routine_sequence_usage ORDER BY 1, 2;
|
||||||
routine_name | sequence_name
|
routine_name | sequence_name
|
||||||
---------------+---------------
|
---------------+---------------
|
||||||
functest_is_5 | functest1
|
functest_is_5 | functest1
|
||||||
functest_is_6 | functest1
|
functest_is_6 | functest1
|
||||||
(2 rows)
|
(2 rows)
|
||||||
|
|
||||||
SELECT routine_name, table_name, column_name FROM information_schema.routine_column_usage;
|
SELECT routine_name, table_name, column_name FROM information_schema.routine_column_usage ORDER BY 1, 2;
|
||||||
routine_name | table_name | column_name
|
routine_name | table_name | column_name
|
||||||
---------------+------------+-------------
|
---------------+------------+-------------
|
||||||
functest_is_7 | functest2 | a
|
functest_is_7 | functest2 | a
|
||||||
(1 row)
|
(1 row)
|
||||||
|
|
||||||
SELECT routine_name, table_name FROM information_schema.routine_table_usage;
|
SELECT routine_name, table_name FROM information_schema.routine_table_usage ORDER BY 1, 2;
|
||||||
routine_name | table_name
|
routine_name | table_name
|
||||||
---------------+------------
|
---------------+------------
|
||||||
functest_is_7 | functest2
|
functest_is_7 | functest2
|
||||||
|
|
|
@ -276,10 +276,11 @@ CREATE FUNCTION functest_IS_7()
|
||||||
SELECT r0.routine_name, r1.routine_name
|
SELECT r0.routine_name, r1.routine_name
|
||||||
FROM information_schema.routine_routine_usage rru
|
FROM information_schema.routine_routine_usage rru
|
||||||
JOIN information_schema.routines r0 ON r0.specific_name = rru.specific_name
|
JOIN information_schema.routines r0 ON r0.specific_name = rru.specific_name
|
||||||
JOIN information_schema.routines r1 ON r1.specific_name = rru.routine_name;
|
JOIN information_schema.routines r1 ON r1.specific_name = rru.routine_name
|
||||||
SELECT routine_name, sequence_name FROM information_schema.routine_sequence_usage;
|
ORDER BY 1, 2;
|
||||||
SELECT routine_name, table_name, column_name FROM information_schema.routine_column_usage;
|
SELECT routine_name, sequence_name FROM information_schema.routine_sequence_usage ORDER BY 1, 2;
|
||||||
SELECT routine_name, table_name FROM information_schema.routine_table_usage;
|
SELECT routine_name, table_name, column_name FROM information_schema.routine_column_usage ORDER BY 1, 2;
|
||||||
|
SELECT routine_name, table_name FROM information_schema.routine_table_usage ORDER BY 1, 2;
|
||||||
|
|
||||||
DROP FUNCTION functest_IS_4a CASCADE;
|
DROP FUNCTION functest_IS_4a CASCADE;
|
||||||
DROP SEQUENCE functest1 CASCADE;
|
DROP SEQUENCE functest1 CASCADE;
|
||||||
|
|
Loading…
Reference in New Issue