May 25, 2012

Comment: Using delayed JOIN to optimize count(*) and LIMIT queries

… in Postgres, it is just one of the tricks of the trade ! I believe the optimizer should be able to move ORDER BY and LIMIT around inside the execution plan by itself but since it isn… table. – since i use ORDER BY + LIMIT, I can then compute the max() or min() (depending on the order) or the relevant row – then…

Comment: Using delayed JOIN to optimize count(*) and LIMIT queries

… in Postgres, it is just one of the tricks of the trade ! I believe the optimizer should be able to move ORDER BY and LIMIT around inside the execution plan by itself but since it isn… table. – since i use ORDER BY + LIMIT, I can then compute the max() or min() (depending on the order) or the relevant row – then…

Post: Heikki Tuuri Innodb answers - Part I

… size drops below this limit, merging it to a neighbor …order is. InnoDB has a similar heuristic for descending index scans. The InnoDB sequential read-ahead is not optimal… there was some work done by DIKU students improving algorithms…tuning of the checkpointing rate? Postgres exposes this data and…