diff --git a/gpdb-doc/dita/client_tool_guides/drivers/windows/win_connect.xml b/gpdb-doc/dita/client_tool_guides/drivers/windows/win_connect.xml index 93b29ce46987f05b2f04a93e8f3d20151061f649..31ceade459bb3786a829c0aa564108777f07899c 100644 --- a/gpdb-doc/dita/client_tool_guides/drivers/windows/win_connect.xml +++ b/gpdb-doc/dita/client_tool_guides/drivers/windows/win_connect.xml @@ -104,7 +104,7 @@ For PDF, the connectivity tools ditamap requires the pdf-note transform --> height="306px"/>
  • For the driver, PostgreSQL Unicode is the recommended choice. Unicode (UTF-8) is the default database encoding for Greenplum Database. There is also a - PostgeSQL ANSI driver which can handle some multi-byte character sets and LATIN + PostgreSQL ANSI driver which can handle some multi-byte character sets and LATIN character sets.
  • Fill in the connection information for your database (on the Greenplum diff --git a/gpdb-doc/dita/client_tool_guides/load/windows/win_load_run.xml b/gpdb-doc/dita/client_tool_guides/load/windows/win_load_run.xml index 95ab89eb6357d2cf8ce60b6c353878e178754de7..0eeca1eb91ef4cd72fde092ae64fbbf9b806759b 100644 --- a/gpdb-doc/dita/client_tool_guides/load/windows/win_load_run.xml +++ b/gpdb-doc/dita/client_tool_guides/load/windows/win_load_run.xml @@ -139,14 +139,14 @@ sequences will encounter errors when loading into Greenplum Database.

    pg_statistic. The query planner uses these statistics to help determine the most efficient execution plans for queries. For example, to collect statistics on a - newly loaded table, run the following on the Greenplum master host:

    psql dbname -c 'ANALYZE mytable;'Vacumming the Database After Load Errors

    The Greenplum loader will stop a load operation if it encounters an + newly loaded table, run the following on the Greenplum master host:

    psql dbname -c 'ANALYZE mytable;'    Vacuuming the Database After Load Errors

    The Greenplum loader will stop a load operation if it encounters an error. When this happens, the target table may already have received earlier rows in the load operation. Although these rows will not be visible or accessible, they still occupy disk space. This may amount to a considerable amount of wasted disk space if the failure happened well into a large load operation. You may wish to invoke the VACUUM command to recover the wasted space. For example, run the following command on -the master host after a load error:

    vacummdb dbname [table_name]

    VACUUM reclaims storage occupied by deleted tuples. In +the master host after a load error:

    vacuumdb dbname [table_name]

    VACUUM reclaims storage occupied by deleted tuples. In normal operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done. Therefore it's recommended to do VACUUM diff --git a/gpdb-doc/dita/ref_guide/extensions/pl_python.xml b/gpdb-doc/dita/ref_guide/extensions/pl_python.xml index f26f55e25776c6643fef526fd877ec9126a1aa60..567886e898d3dd04a7b764eebb46318bafa1e4a6 100644 --- a/gpdb-doc/dita/ref_guide/extensions/pl_python.xml +++ b/gpdb-doc/dita/ref_guide/extensions/pl_python.xml @@ -375,7 +375,7 @@ python setup.py build && python setup.py install

    • commands download tar files into the directory packages:wget --directory-prefix=packages http://github.com/xianyi/OpenBLAS/tarball/v0.2.8 wget --directory-prefix=packages http://sourceforge.net/projects/numpy/files/NumPy/1.8.0/numpy-1.8.0.tar.gz/download

    -

    Distribute the software to the Geeenplum Database hosts. For example, if you download the +

    Distribute the software to the Greenplum Database hosts. For example, if you download the software to /home/gpadmin/packages these commands create the directory on the hosts and copies the software to hosts for the hosts listed in the gpdb_remotes diff --git a/gpdb-doc/dita/ref_guide/function-summary.xml b/gpdb-doc/dita/ref_guide/function-summary.xml index 779734f5f8fcaa3a899fc37fc9224d81e42b9c9e..32e57bc28e20079fd00e29a09c44751a70075bc2 100644 --- a/gpdb-doc/dita/ref_guide/function-summary.xml +++ b/gpdb-doc/dita/ref_guide/function-summary.xml @@ -1164,7 +1164,7 @@ PERCENTILE_CONT (0.5) WITHIN GROUP (ORDER BY salary DESC) "Median_cont"; FROM employees GROUP BY department_id; - Performs an inverse distirbution function that assumes a + Performs an inverse distribution function that assumes a continuous distribution model. It takes a percentile value and a sort specification and returns the same datatype as the numeric datatype of the argument. This returned value is a computed result after performing linear interpolation. Null are ignored @@ -1187,7 +1187,7 @@ PERCENTILE_DISC (0.5) WITHIN GROUP (ORDER BY salary DESC) "Median_desc"; FROM employees GROUP BY department_id; - Performs an inverse distirbution function that assumes a + Performs an inverse distribution function that assumes a discrete distribution model. It takes a percentile value and a sort specification. This returned value is an element from the set. Null are ignored in this calculation. diff --git a/gpdb-doc/dita/ref_guide/functions/aggregate.xml b/gpdb-doc/dita/ref_guide/functions/aggregate.xml index 97f122090cfd7a6ad05130a5dac25becab5abfd5..3b5787768f1bdef86aed92efaae15743dbed9a11 100644 --- a/gpdb-doc/dita/ref_guide/functions/aggregate.xml +++ b/gpdb-doc/dita/ref_guide/functions/aggregate.xml @@ -513,7 +513,7 @@ percentile_cont (0.5) WITHIN GROUP (ORDER BY salary DESC) "Median_cont"; FROM employees GROUP BY department_id; - Performs an inverse distirbution function that assumes a + Performs an inverse distribution function that assumes a continuous distribution model. It takes a percentile value and a sort specification and returns the same datatype as the numeric datatype of the argument. This returned value is a computed result after performing linear interpolation. Null are ignored