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?.
CREATE TABLE
INSERT 0 2
CREATE TABLE
INSERT 0 6
CREATE INDEX
post_id author_id title created_at
3 1 Johns third post 2021-01-03 00:00:00+00
2 1 Johns second post 2021-01-02 00:00:00+00
6 2 Mikes third post 2021-01-03 00:00:00+00
5 2 Mikes second post 2021-01-02 00:00:00+00
SELECT 4
SET
QUERY PLAN
Nested Loop (cost=14.95..10413.42 rows=1270 width=94) (actual time=0.078..0.086 rows=4 loops=1)
  Buffers: shared hit=5 read=1
  -> Bitmap Heap Scan on author a (cost=14.82..37.52 rows=1270 width=4) (actual time=0.020..0.021 rows=2 loops=1)
        Heap Blocks: exact=1
        Buffers: shared hit=2
        -> Bitmap Index Scan on author_pkey (cost=0.00..14.50 rows=1270 width=0) (actual time=0.012..0.012 rows=2 loops=1)
              Buffers: shared hit=1
  -> Limit (cost=0.13..8.15 rows=1 width=94) (actual time=0.029..0.030 rows=2 loops=2)
        Buffers: shared hit=3 read=1
        -> Index Scan Backward using post_author_id_created_at_idx on post (cost=0.13..8.15 rows=1 width=94) (actual time=0.028..0.028 rows=2 loops=2)
              Index Cond: (author_id = a.author_id)
              Buffers: shared hit=3 read=1
Planning Time: 0.100 ms
Execution Time: 0.145 ms
EXPLAIN