I've noticed, updating from SA 11.0.1.2584 to 11.0.1.3027 or 11.0.1.3113, that the queries on some of our views are really slow.
(please don't mind the columns, it's just an example).
I was expecting Sybase to first filter by "someID" (which it does, on 11.0.1.2584). Since the update, though, for some reason we have yet to find or understand, this doesn't happen.
The query time grew from a couple of seconds to over 12 minutes.
For example, given the following hierarchy: VIEW_2 <- VIEW_1 <- TABLE_1, with TABLE_1 containing (product_id, valid_from, valid_to). A query on TABLE_1 with a filter on the product_id and validity, runs as expected (that is, fast). Same for a query with an identical where clause on VIEW_1. A third identical query on VIEW_2, however, first builds VIEW_1 completely and only applies the filter afterwards. This leads to significant performance issues.
I'll add that proper indexes are used and that the statistics are up to date.
Is there a change introduced by the updates that I'm not aware of and which is not highlighted in the release notes/comes from an older updated, related to how query plans work on views/predicate push down etc work?
We've also encountered another oddity - if TABLE_1 calls "list" for some of its columns, similar performance issues arise.
Please post a "graphical plan with statistics" for a slow query. If this forum's software won't let you post the *.saplan file, please email it to me breck dot carter at gmail dot com.
For more information about graphical plans, see this google search.
I'm not sure if I can attach files - I'll check the forum options again, I might have missed something.
Also tested with SA 16, with identical performance issues.
> please email it to me breck dot carter at gmail dot com.
With my testing, I see consistently (10.0.1(3415), 11.0.1(2044), 11.0.1(2584), 11.0.1(2878)) that the predicate V.manager_id=501 is evaluated after the GROUP BY if there is an ORDER BY in the LIST aggregate. Without the ORDER BY, the predicate is evaluated before the GROUP BY. This is a known restriciton of our predicate pushdown semantic transformations. In discussions with colleagues we have not been able to identify what would have ever allowed that predicate pushdown correctly, but we surmised that perhaps there was a software defect that unintentionally allowed the pushdown. While it is safe in this case, the logic to ensure it is safe is not part of the current servers and the server should not be doing the predicate pushdown here. This is an enhancement that we are considering. The limitation currently affects any aggregate with an ORDER BY (array_agg, list, xmlagg) and any window function.
Thank you, I appreciate your answer - that is basically what I wanted to know.
As a note: our view represents a union. I did some more testing, and this causes causes the predicate pushdown in 11.0.1.2485.