Changes between Version 9 and Version 10 of P9
- Timestamp:
- 05/28/26 00:56:58 (4 hours ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
P9
v9 v10 187 187 * booking tables are joined using hash joins because of the multiple LEFT JOIN operations 188 188 189 * HashAggregate:189 * !HashAggregate: 190 190 * aggregation is performed after all joins are completed 191 191 … … 381 381 * attendance records are matched with event and wedding relations 382 382 383 * HashAggregate:383 * !HashAggregate: 384 384 * PostgreSQL groups attendance rows by venue and wedding information 385 385 … … 584 584 * guests are matched with RSVP and attendance records 585 585 586 * HashAggregate:586 * !HashAggregate: 587 587 * PostgreSQL groups records by wedding and event before calculating conversion metrics 588 588 … … 1295 1295 || Hash Join || PostgreSQL builds a hash table to join larger datasets || 1296 1296 || 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 || 1298 1298 || Sort || PostgreSQL sorts rows for ORDER BY or aggregation operations || 1299 1299 1300 1300 For Phase 6 reports, the most common expected elements are: 1301 1301 * Hash Join 1302 * HashAggregate1302 * !HashAggregate 1303 1303 * Index Scan 1304 1304 * Seq Scan on small tables
