wjohnsonbynder commented on PR #106: URL: https://github.com/apache/incubator-pekko-persistence-jdbc/pull/106#issuecomment-1938712794
Looks I wasted a your time, sorry for that. I did some digging. Postgres is great DB and the query plan for either optimize to the best version. I think my original timing ran with the order by in the subquery. Orderby on a subquery is removed so the "increased performance" was the query not running the order by at all. We have a large event journal and the order by on this query isn't fast. I need to dig into the query some more and see what the parameters are and see if we can optimize the size of the result set or how often our projections make the query. Closing this out and the issue. Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
