From a4fe924936fe623ff95e6aa050b8fd7d22dbbb84 Mon Sep 17 00:00:00 2001 From: "dgrowley@gmail.com" Date: Mon, 9 Apr 2018 15:43:32 +1200 Subject: [PATCH v2] Remove mention of constraint_exclusion in partitioning docs As of 9fdb675fc5d2, this GUC now no longer has an affect on partition pruning. --- doc/src/sgml/ddl.sgml | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index feb2ab7792..eed8753e24 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -3194,13 +3194,14 @@ CREATE INDEX ON measurement (logdate); - - - Ensure that the - configuration parameter is not disabled in postgresql.conf. - If it is, queries will not be optimized as desired. - - + + + Ensure that the + configuration parameter is not disabled in postgresql.conf. + While enabling it is not required for select queries, not doing so will result + in update and delete queries to not be optimized as desired. + + @@ -3767,10 +3768,12 @@ ANALYZE measurement; - Constraint exclusion is a query optimization technique - that improves performance for partitioned tables defined in the - fashion described above (both declaratively partitioned tables and those - implemented using inheritance). As an example: + Constraint exclusion is a query optimization + technique that improves performance for partitioned tables defined in the + fashion described above. While it is used only for update and delete + queries in the case of declaratively partitioned tables, it is used for all + queries in the case of table partitioning implemented using inheritance. + As an example: SET constraint_exclusion = on; -- 2.11.0