Commit2f30d5a

committed

My recent optimizer changes caused a different plan to

be picked for one of the complex joins in rules test ... leading toa different output ordering ...

1 parent9e7e29e commit2f30d5aCopy full SHA for 2f30d5a

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1022,9 +1022,9 @@ QUERY: SELECT * FROM shoelace_log;`
`1022`	`1022`	`sl_name \|sl_avail\|log_who \|log_when`
`1023`	`1023`	`----------+--------+--------+--------`
`1024`	`1024`	`sl7 \| 6\|Al Bundy\|epoch`
`1025`		`-sl3 \| 10\|Al Bundy\|epoch`
`1026`	`1025`	`sl6 \| 20\|Al Bundy\|epoch`
`1027`	`1026`	`sl8 \| 21\|Al Bundy\|epoch`
	`1027`	`+sl3 \| 10\|Al Bundy\|epoch`
`1028`	`1028`	`(4 rows)`
`1029`	`1029`
`1030`	`1030`	`QUERY: CREATE VIEW shoelace_obsolete AS`

Comments

(0)