Docs gporca utility notice (#7630)

* Docs: fixing several broken links * Docs: fixing several broken links * Adding info about GPORCA support notice * add missing comma

Docs gporca utility notice (#7630)
* Docs: fixing several broken links * Docs: fixing several broken links * Adding info about GPORCA support notice * add missing comma
a9452d5c · David Yozie · 674380d6 · a9452d5c · a9452d5c
2 changed file
--- a/gpdb-doc/dita/admin_guide/query/topics/query-piv-opt-limitations.xml
+++ b/gpdb-doc/dita/admin_guide/query/topics/query-piv-opt-limitations.xml
@@ -16,7 +16,10 @@
  <topic id="topic_kgn_vxl_vp">
    <title>Unsupported SQL Query Features</title>
    <body>
-      <p>These are unsupported features when GPORCA is enabled (the default): <ul id="ul_ndm_gyl_vp">
+      <p>Certain query features are not supported with the default GPORCA optimizer. When an
+        unsupported query is executed, Greenplum logs this notice along with the query
+        text:<codeblock>Feature not supported by the Pivotal Query Optimizer: UTILITY command</codeblock></p>
+      <p>These features are unsupported when GPORCA is enabled (the default): <ul id="ul_ndm_gyl_vp">
          <li>Indexed expressions (an index defined as expression based on one or more columns of
            the table)</li>
          <li>GIN indexing method. GPORCA supports only B-tree, bitmap, and GiST indexes. GPORCA

--- a/gpdb-doc/dita/admin_guide/textsearch/controlling.xml
+++ b/gpdb-doc/dita/admin_guide/textsearch/controlling.xml
@@ -90,7 +90,7 @@
      <codeblock>to_tsquery([<i>config</i> regconfig, ] <i>querytext</i> text) returns tsquery</codeblock>
      <p><codeph>to_tsquery</codeph> creates a <codeph>tsquery</codeph> value from <i>querytext</i>,
        which must consist of single tokens separated by the Boolean operators
-          <codeph>&amp;</codeph> (AND), <codeph>|</codeph> (OR) and <codeph>!</codeph>(NOT). These
+          <codeph>&amp;</codeph> (AND), <codeph>|</codeph> (OR), and <codeph>!</codeph>(NOT). These
        operators can be grouped using parentheses. In other words, the input to
          <codeph>to_tsquery</codeph> must already follow the general rules for
          <codeph>tsquery</codeph> input, as described in <xref