Re: [HACKERS] Runtime Partition Pruning
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Beena Emerson <memissemerson@gmail.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>, amul sul <sulamul@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
Dilip Kumar <dilipbalaut@gmail.com>
Date: 2017-12-01T19:04:37Z
Lists: pgsql-hackers
On Fri, Dec 1, 2017 at 6:20 AM, Beena Emerson <memissemerson@gmail.com> wrote: > David Q1: > postgres=# explain analyse execute ab_q1 (3,3); --const > QUERY PLAN > --------------------------------------------------------------------------------------------------------- > Append (cost=0.00..43.90 rows=1 width=8) (actual time=0.006..0.006 > rows=0 loops=1) > -> Seq Scan on ab_a3_b3 (cost=0.00..43.90 rows=1 width=8) (actual > time=0.005..0.005 rows=0 loops=1) > Filter: ((a = 3) AND (b = 3)) > Planning time: 0.588 ms > Execution time: 0.043 ms > (5 rows) I think the EXPLAIN ANALYZE input should show something attached to the Append node so that we can tell that partition pruning is in use. I'm not sure if that is as simple as "Run-Time Partition Pruning: Yes" or if we can give a few more useful details. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Initialize ExprStates once in run-time partition pruning
- 1957f8dabf8d 11.0 landed
-
Add bms_prev_member function
- 5c0675215e15 11.0 landed
-
Support partition pruning at execution time
- 499be013de65 11.0 landed
-
Document partprune.c a little better
- 971d7ddbe19a 11.0 landed
-
Fix crash in pg_replication_slot_advance
- 6f1d723b6359 11.0 cited
-
Add parallel-aware hash joins.
- 1804284042e6 11.0 cited
-
Fix typo.
- 487a0c1518af 11.0 cited
-
Allow --with-bonjour to work with non-macOS implementations of Bonjour.
- 9b9cb3c4534d 11.0 cited
-
Mention need for --no-inc-recursive in rsync command
- 2c74e6c1dcc5 11.0 cited