<commit_before><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="topic_dt3_fkv_r4">
  <title>System Configuration</title>
  <shortdesc>Requirements and best practices for system administrators who are configuring Greenplum
    Database cluster hosts.</shortdesc>
  <body>
    <p>Configuration of the Greenplum Database cluster is usually performed as root.</p>
    <section id="file_system"><commit_msg>adding best practice note for setting timezone (#5095)<commit_after><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="topic_dt3_fkv_r4">
  <title>System Configuration</title>
  <shortdesc>Requirements and best practices for system administrators who are configuring Greenplum
    Database cluster hosts.</shortdesc>
  <body>
    <p>Configuration of the Greenplum Database cluster is usually performed as root.</p>
    <section id="topic_fvc_zh1_b2b">
      <title>Configuring the Timezone</title>
      <p>Greenplum Database selects a timezone to use from a set of internally stored PostgreSQL
        timezones. The available PostgreSQL timezones are taken from the Internet Assigned Numbers
        Authority (IANA) Time Zone Database, and Greenplum Database updates its list of available
        timezones as necessary when the IANA database changes for PostgreSQL. </p>
      <p>Greenplum selects the timezone by matching a PostgreSQL timezone with the user specified
        time zone, or the host system time zone if no time zone is configured. For example, when
        selecting a default timezone, Greenplum uses an algorithm to select a PostgreSQL timezone
        based on the host system timezone files. If the system timezone includes leap second
        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
          <codeph>US/Pacific</codeph>.<codeblock># gpconfig -s TimeZone
# gpconfig -c TimeZone '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>
    </section>

    <section id="file_system">
{'fraction_non_alphanumeric': 0.06970684039087947, 'fraction_numerical': 0.005211726384364821, 'mean_word_length': 3.8979266347687402, 'pattern_counts': {'":': 0, '<': 45, '<?xml version=': 2, '>': 45, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '921545', 'n_tokens_mistral': 838, 'n_tokens_neox': 800, 'n_words': 350}