docs - minor edits to docs.
information, Greenplum Database cannot match the system timezone with a PostgreSQL timezone.
In this case, Greenplum Database calculates a "best match" with a PostgreSQL timezone based
on information from the host system.</p>
- <p>As a best practice, configure the Greenplum Database and the host system to use a known,
- supported timezone. This prevents Greenplum Database from recalculating a "best match"
- timezone each time the cluster is restarted, using the current system timezone and Greenplum
- timezone files (which may have been updated from the IANA database since the last restart).
- Use the <codeph>gpconfig</codeph> utility to show and set the Greenplum Database timezone.
- For example, these commands show the Greenplum Database timezone and set the timezone to
+ <p>As a best practice, configure Greenplum Database and the host systems to use a known,
+ supported timezone. This sets the timezone for the Greenplum Database master and segment
+ instances, and prevents Greenplum Database from recalculating a "best match" timezone each
+ time the cluster is restarted, using the current system timezone and Greenplum timezone
+ files (which may have been updated from the IANA database since the last restart). Use the
+ <codeph>gpconfig</codeph> utility to show and set the Greenplum Database timezone. For
+ example, these commands show the Greenplum Database timezone and set the timezone to
<codeph>US/Pacific</codeph>.<codeblock># gpconfig -s TimeZone
-# gpconfig -c TimeZone 'US/Pacific'</codeblock>You
+# gpconfig -c TimeZone -v 'US/Pacific'</codeblock>You
must restart Greenplum Database after changing the timezone. The command <codeph>gpstop
-ra</codeph> restarts Greenplum Database. The catalog view
<codeph>pg_timezone_names</codeph> provides Greenplum Database timezone information.</p>
