Changes between Version 9 and Version 10 of P9


Ignore:
Timestamp:
05/28/26 00:56:58 (4 hours ago)
Author:
193284
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • P9

    v9 v10  
    187187  * booking tables are joined using hash joins because of the multiple LEFT JOIN operations
    188188
    189 * HashAggregate:
     189* !HashAggregate:
    190190  * aggregation is performed after all joins are completed
    191191
     
    381381  * attendance records are matched with event and wedding relations
    382382
    383 * HashAggregate:
     383* !HashAggregate:
    384384  * PostgreSQL groups attendance rows by venue and wedding information
    385385
     
    584584  * guests are matched with RSVP and attendance records
    585585
    586 * HashAggregate:
     586* !HashAggregate:
    587587  * PostgreSQL groups records by wedding and event before calculating conversion metrics
    588588
     
    12951295|| Hash Join || PostgreSQL builds a hash table to join larger datasets ||
    12961296|| Nested Loop || PostgreSQL repeatedly scans one relation for each row of another relation ||
    1297 || HashAggregate || PostgreSQL performs grouping and aggregation using a hash table ||
     1297|| !HashAggregate || PostgreSQL performs grouping and aggregation using a hash table ||
    12981298|| Sort || PostgreSQL sorts rows for ORDER BY or aggregation operations ||
    12991299
    13001300For Phase 6 reports, the most common expected elements are:
    13011301* Hash Join
    1302 * HashAggregate
     1302* !HashAggregate
    13031303* Index Scan
    13041304* Seq Scan on small tables