Explore >> Select a destination
|
You are here 
|
nick.zoic.org | ||
| | | | |
stormatics.tech
|
|
| | | | | pg_stat_statement is the essential extension that provides valuable insights into the query performance of a PostgreSQL database. | |
| | | | |
highperformancesqlite.com
|
|
| | | | | I learned about creating composite indexes on multiple columns in a database, like first name, last name, and birthday, and how important the order is in these indexes. The rule is to use the index from left to right without skipping any columns, and it stops when it hits a range condition. By understanding these rules, we can optimize indexes for better query performance by placing common equality conditions at the beginning and range conditions at the end. | |
| | | | |
postgrespro.com
|
|
| | | | | ||
| | | | |
orastory.wordpress.com
|
|
| | | There have been some interesting posts from Marcin Przepiorowski and Kerry Osborne about mapping sql plan management (spm) baselines to a corresponding sql id. The key to sql plan baselines (DBA_SQL_PLAN_BASELINES) is SIGNATURE. And why signature? It's not just another change to the key to identifying sql statements (HASH_VALUE -> (NEW_)HASH_VALUE / OLD_HASH_VALUE -> SQL_ID).... | ||
