add batch remove batch split batch comment selection show hidden batches hide batch highlight batch
db<>fiddle
donate feedback about
By using db<>fiddle, you agree to license everything you submit by Creative Commons CC0.
Help with an interesting Postgres question: Why isn't an Index Only Scan used on a partition accessed via the parent table?.
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
1 rows affected
title found_in_regions
d 1
a 2
b 2
f 1
QUERY PLAN
HashAggregate (cost=80.19..82.19 rows=200 width=126)
  Group Key: t.title
  -> Hash Join (cost=60.85..77.54 rows=530 width=122)
        Hash Cond: (t.unit_id = u.id)
        -> Seq Scan on unit_usage t (cost=0.00..15.30 rows=530 width=122)
        -> Hash (cost=32.60..32.60 rows=2260 width=8)
              -> Seq Scan on unit u (cost=0.00..32.60 rows=2260 width=8)
QUERY PLAN
HashAggregate (cost=137.59..139.59 rows=200 width=126)
  Group Key: t.title
  -> Merge Join (cost=39.44..134.94 rows=530 width=122)
        Merge Cond: (u.id = t.unit_id)
        -> Index Scan using unit_pkey on unit u (cost=0.15..82.06 rows=2260 width=8)
        -> Sort (cost=39.28..40.61 rows=530 width=122)
              Sort Key: t.unit_id
              -> Seq Scan on unit_usage t (cost=0.00..15.30 rows=530 width=122)