From: | Mark Steben <mark(dot)steben(at)drivedominion(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Version 11 partitioning: Constraint exclusion vs Partition Pruning |
Date: | 2019-09-04 20:15:04 |
Message-ID: | CADyzmyyd7GNThHRWdEudtxDr8OXriQu8XUdEon0WtqAQ-tq89w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Good afternoon,
I am contemplating implementing partitioning in Postgres v 11. I am
reading the documentation and came across this statement in the Constraint
Exclusion section:
*Constraint exclusion only works when the query's WHERE clause contains
constants (or externally supplied parameters). *
Is this true also in Partition pruning? I don't see a similar statement in
that section.
If we can place variables in the where clause and have partitioning still
work, that would be an awesome enhancement. I see that Declarative
partitioning was implemented in version 10 and a whole raft of partitioning
enhancements in version 11. (We are currently at 9.4 and want to upgrade
as well).
--
*Mark Steben*
Database Administrator
@utoRevenue <http://www.autorevenue.com/> | Autobase
<http://www.autobase.net/>
CRM division of Dominion Dealer Solutions
95D Ashley Ave.
West Springfield, MA 01089
t: 413.327-3045
f: 413.383-9567
www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com <http://www.autorevenue.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Ferrari | 2019-09-05 07:01:07 | Re: overwrote THE 'postgres' database - how to recover |
Previous Message | Guillaume Lelarge | 2019-09-04 19:52:13 | Re: overwrote THE 'postgres' database - how to recover |