提交 2f30d5a3 编写于 作者: T Tom Lane

My recent optimizer changes caused a different plan to

be picked for one of the complex joins in rules test ... leading to
a different output ordering ...
上级 9e7e29e6
...@@ -1022,9 +1022,9 @@ QUERY: SELECT * FROM shoelace_log; ...@@ -1022,9 +1022,9 @@ QUERY: SELECT * FROM shoelace_log;
sl_name |sl_avail|log_who |log_when sl_name |sl_avail|log_who |log_when
----------+--------+--------+-------- ----------+--------+--------+--------
sl7 | 6|Al Bundy|epoch sl7 | 6|Al Bundy|epoch
sl3 | 10|Al Bundy|epoch
sl6 | 20|Al Bundy|epoch sl6 | 20|Al Bundy|epoch
sl8 | 21|Al Bundy|epoch sl8 | 21|Al Bundy|epoch
sl3 | 10|Al Bundy|epoch
(4 rows) (4 rows)
QUERY: CREATE VIEW shoelace_obsolete AS QUERY: CREATE VIEW shoelace_obsolete AS
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册